Creates a new activity for a specified account. Use this tool to add a new activity to an account by providing the account's internal or external ID. It will confirm the creation of the activity. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a highlight for a specified account. This tool is used to create a highlight for an account, using either an internal account ID in UUID format or an external ID in string format. It should be called when there is a need to add or update a highlight for an account. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Generate an AI response for a specific issue. This tool creates an AI-generated response for a given issue by specifying the issue ID. It should be called when an automated response is required for issue resolution or documentation. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new custom field in the system. Use this tool to add a custom field to your database or application configuration. It allows for extending the available data fields to include additional, personalized information. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Creates a note on an issue to track additional details. This tool should be called when there's a need to add a note or comment to an existing issue to provide further information or updates. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a reply to an existing issue. Use this tool to add a comment or response to an existing issue when interaction or follow-up is required. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create an issue thread for an existing issue. Use this tool to initiate a discussion thread related to a specific issue by providing the issue ID. This helps in organizing conversations around particular issues efficiently.

Create and publish an article in a knowledge base. This tool allows the creation of a new article in a specified knowledge base, including optional translations. If the article is set to publish, translations will also be published. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new milestone in a project management system. This tool is used to create a milestone within a project management application. It should be called when there's a need to add a new milestone to track progress or set goals in a project. The tool confirms the creation of the milestone.

Creates a new user account. This tool should be called to create a new user account when registration or account opening is requested. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new collection in a knowledge base. This tool is used to create a new collection within a specified knowledge base by providing the knowledge base ID. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new contact in the system. This tool creates a new contact by sending the necessary details to the endpoint. Use it when you need to add a new person's contact information to the database. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new issue in the system. This tool is used to create a new issue in the system. It should be called whenever there's a need to log or track a new issue or task. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new project seamlessly. This tool is used to create a new project. It should be called when a user wants to initialize or start a new project within a system.

Create a new tag within the system. This tool is used to create a new tag by sending a POST request to the /tags endpoint. It should be called when a user wants to add a new tag to the system for organizational or categorization purposes. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new team for collaboration. Use this tool to create a new team on the platform, facilitating collaboration and organization. It returns details about the newly created team.

Create a new route redirect for a knowledge base. This tool is used to create a new route redirect within a specified knowledge base. It should be called when you need to add a redirect to manage or alter the routing within a knowledge base. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new task with specified parameters. Use this tool to create a task. It should be called when a new task needs to be added to the system, specifying necessary parameters.

Create a new training data configuration. Call this tool to set up a new training data configuration for your application. It is used when you need to initialize or update your training data setup.

Delete an existing account. This tool deletes an existing account based on the provided account ID. Call this tool when you need to permanently remove an account.

Delete a specific highlight from an account. Use this tool to delete a specific highlight by providing the account ID and highlight ID. It should be called when a user wants to remove a highlight linked to an account.

Delete an existing article from a knowledge base. Call this tool to remove an article from a knowledge base by specifying the knowledge base and article IDs.

Delete an existing contact by ID. This tool deletes a contact by its ID. It should be called when a user needs to remove a contact from the system.

Delete an existing project using its ID. Use this tool to delete an existing project by providing the project ID. It allows you to manage and remove projects that are no longer needed.

Delete an existing tag by ID. Use this tool to delete an existing tag by specifying its ID. It confirms whether the deletion was successful.

Delete an existing issue by ID. Use this tool to delete an issue from the system by providing its ID. It is ideal for scenarios where issues need to be managed or cleaned up.

Delete a specific milestone using its ID. Use this tool to remove a milestone by providing its unique ID. This operation is irreversible and should be used when a milestone is no longer needed.

Delete an existing task by ID. Use this tool to delete a specific task by its ID. Call it when you need to remove a task permanently from the system.

Deletes documents from a training data configuration. Use this tool to delete documents from a specific training data configuration by providing the relevant ID. This tool is helpful when managing or updating data sets for training purposes.

Retrieve all available tags. Use this tool to obtain a comprehensive list of all tags. It is ideal for scenarios where you need to display or manage tags.

Retrieve the list of available teams. Use this tool to get a list of all teams from the service. Useful for displaying team information or selecting a team from the list.

Retrieve an account's details using its ID or external ID. Call this tool to obtain detailed information about an account by providing either the account ID or external ID.

Retrieve a list of accounts from the service. This tool fetches a complete list of accounts from the Pylon service. It should be called when you need to obtain account information.

Retrieve all contacts from the service. This tool retrieves all contacts using the Pylon service. It should be called when there's a need to fetch a complete list of contacts from the service.

Retrieve all custom fields from the system. This tool is used to get a complete list of custom fields. It should be called when you need information about available custom fields.

Retrieve a specific collection using its ID. Use this tool to obtain detailed information about a particular collection by supplying the collection ID. The collection belongs to a specific knowledge base. Ideal for retrieving specific datasets or information collections within larger systems.

Retrieve contact details using the contact ID. This tool fetches and returns contact details by querying with a specified contact ID. Use it when you need to obtain specific contact information.

Retrieve a list of custom activity types. Use this tool to get a list of custom activity types that are available. It should be called when there's a need to know what custom activity types exist.

Retrieve a custom field by its ID. Use this tool to obtain details of a specific custom field using its unique identifier.

Retrieve issue details using its ID or number. Use this tool to access details of an issue by providing its specific ID or number. Ideal for tasks requiring detailed issue information retrieval in issue tracking systems.

Get followers of a specific issue to manage participation. This tool retrieves the list of users who are following a specified issue. Use this tool when you need to know who is engaging with or interested in updates about an issue.

Retrieve messages for a specific issue. This tool is used to obtain all messages associated with a particular issue, identified by its ID.

Retrieve a list of issues. Call this tool to get a list of issues from the Pylon service, useful for tracking or managing tasks and bugs.

Retrieve all issue statuses from the system. Use this tool to get a complete list of issue statuses available in the project management system. This can help with tracking and managing project workflows efficiently.

Retrieve threads for a specific issue. Call this tool to get all threads associated with a particular issue using its ID. Useful for tracking conversations or discussions related to an issue.

Retrieve a knowledge base using its ID. Use this tool to fetch information about a specific knowledge base by providing its ID.

Retrieve all available knowledge bases. This tool is called to get a list of all knowledge bases from the Pylon service.

Retrieve details of the current organization. Use this tool to get information about the organization linked to the given API token, like name, address, and other relevant details.

Retrieve tag details using a specified ID.

Retrieve team details using the team's ID. Use this tool to get detailed information about a team by specifying its unique ID.

Retrieve detailed information about a ticket form. Call this tool to obtain detailed information for a specific ticket form by providing its ID.

Retrieve a list of ticket forms available. This tool fetches a list of ticket forms, which can be used to understand the structure of available forms for managing tickets. It should be called when you need to review or select from ticket forms.

Retrieve user details using their unique ID. Use this tool to get detailed information about a user by providing their unique ID.

Get a list of all user roles. Use this tool to retrieve a comprehensive list of all user roles. It is useful for managing and understanding user permissions.

Import an issue into the system. This tool is used to import an issue into the Pylon system. Use it when you need to add new issues by importing them through a specified format or integration. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Import messages into an existing issue. Use this tool to import new messages onto an existing issue, facilitating better organization and tracking within issue management systems. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Import a new contact into the system. Use this tool to import a new contact into the system whenever you need to add contact information. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Link or unlink external issues to an internal issue. Use this tool to link external issues to an internal issue or unlink them by specifying the operation type. Ideal for managing issue relationships between different systems. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

List all collections in a knowledge base. Use this tool to retrieve all collections within a specific knowledge base. Useful for accessing organized information in structured formats.

Fetches all training data configurations for the organization. Use this tool to retrieve a comprehensive list of training data configurations associated with the organization. Ideal for managing or reviewing training datasets.

Fetches a list of users. Use this tool to retrieve a list of all users. It provides an overview of the users available in the system.

Removes or hides the content of a specified message. Use this tool to redact (remove or hide) the content of a message identified by a specific message ID within an issue. This is useful for maintaining privacy or correcting errors.

Retrieve a training data configuration by ID. This tool retrieves the details of a specific training data configuration using its unique ID. It should be called when you need to access the configuration settings or specifications for a particular training dataset.

Search and filter accounts using various criteria. This tool allows searching and filtering of accounts with specific criteria such as domains, tags, name, external IDs, and custom fields. It supports operators like 'contains', 'equals', 'in', 'not_in', and others, enabling detailed account queries. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Search for contacts using various filter criteria. This tool allows you to search for contacts by applying filters on fields such as id, email, custom fields, and account_id. Use it to find specific contacts based on these criteria. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Search for issues using various filters and criteria. Use this tool to search for issues by applying filters such as creation date, account ID, requester ID, status, tags, title, and more. Suitable for retrieving specific issues according to predefined criteria and operators. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Search for users by email with filter options. Use this tool to find users by filtering their email with options such as 'equals', 'in', or 'not_in'. It should be called when there's a need to retrieve user information based on specific email criteria. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Temporarily pause notifications for an issue. Use this tool to snooze notifications for a specific issue temporarily. It is helpful when you want to focus elsewhere without getting alerts for the issue. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update details of an existing account. Use this tool to modify the information of an existing account by providing the account ID and new details. It should be called when account information needs to be updated. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Updates the highlight for a specified account. Use this tool to update the highlight information for a given account by specifying either the internal account ID or an external ID. Appropriate when modifications to account highlights are needed.

Update the content of an existing article. Use this tool to modify the content or details of an existing article in a knowledge base when updates are needed. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Updates an existing contact's information. Use this tool to update the details of an existing contact when modifications are needed. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update a custom field in a record. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update an existing tag's information. Use this tool to modify the details of an already existing tag. It should be called when changes to tag attributes are needed.

Update details of an existing team. Use this tool to modify the information of an existing team. Ideal for updating team names, members, or other details.

Update details of an existing issue. Use this tool to modify information for an already existing issue when changes or corrections are needed. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Add or remove followers for an issue. This tool allows you to add or remove followers to a specific issue. Use it when managing the users who should receive notifications about updates on an issue. Set the operation field to "remove" to remove followers.

Updates the details of a specific milestone. This tool is used to update information for a specific milestone in a project, identified by its ID.

Update multiple accounts simultaneously. Use this tool to update details for multiple accounts in one request. It is helpful for batch processing of account modifications. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update the details of an existing project. Use this tool to modify the information of an existing project by providing the project ID and necessary updates. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path, query parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path, query parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Update the details of an existing task. Use this tool to modify the information of a specific task by providing its ID. Ideal for updating any details like status, description, or due date.

Update a user's profile information. This tool updates the information of a user identified by a specific ID. It should be called when changes to a user's profile are needed, such as updating personal details or contact information.