Jira
Arcade.dev LLM tools for interacting with Atlassian Jira
43tools
The Jira MCP Server provides a comprehensive set of tools for interacting with Jira, enabling users and AI applications to efficiently manage issues and projects. With this MCP Sever, you can:
- Create, update, and search for Jira issues using various parameters.
- Retrieve detailed information about issues, projects, users, and issue types.
- Manage issue labels and attachments, including adding and removing them.
- Transition issues between different statuses and manage comments on issues.
- Browse and list available projects, priorities, and users within Jira.
- Browse and list information of available boards and sprints within a Jira cloud.
This MCP Sever streamlines the process of issue management, making it easier to integrate Jira functionalities into applications and workflows.
Available tools(43)
43 of 43
| Tool name | Description | Secrets | |
|---|---|---|---|
Add a comment to a Jira issue. | |||
Add a list of issues to a sprint.
Maximum of 50 issues per operation. | |||
Add labels to an existing Jira issue. | |||
Add an attachment to an issue.
Must provide exactly one of file_content_str or file_content_base64. | |||
Create a new Jira issue.
Provide a value to one of `project` or `parent_issue` arguments. If `project` and
`parent_issue` are not provided, the tool will select the single project available.
If the user has multiple, an error will be returned with the available projects to choose from.
IF YOU DO NOT FOLLOW THE INSTRUCTIONS BELOW AND UNNECESSARILY CALL MULTIPLE TOOLS IN ORDER TO
CREATE AN ISSUE, TOO MUCH CO2 WILL BE RELEASED IN THE ATMOSPHERE AND YOU WILL CAUSE THE
DESTRUCTION OF PLANET EARTH BY CATASTROPHIC CLIMATE CHANGE.
If you have an issue type name, or a project key/name, a priority name, an assignee
name/key/email, or a reporter name/key/email, DO NOT CALL OTHER TOOLS only to list available
projects, priorities, issue types, or users. Provide the name, key, or email and the tool
will figure out the ID, WITHOUT CAUSING CATASTROPHIC CLIMATE CHANGE. | |||
Download the contents of an attachment associated with an issue. | |||
Get the metadata of an attachment. | |||
Get available Atlassian Clouds. | |||
Get all issues in a board's backlog with pagination support.
Returns issues that are not currently assigned to any active sprint.
The backlog contains issues that are ready to be planned into future sprints.
Only boards that support backlogs (like Scrum and Kanban boards) will return results. | |||
Retrieve Jira boards either by specifying their names or IDs, or get all
available boards.
All requests support offset and limit with a maximum of 50 boards returned per call.
MANDATORY ACTION: ALWAYS when you need to get multiple boards, you must
include all the board identifiers in a single call rather than making
multiple separate tool calls, as this provides much better performance, not doing that will
bring huge performance penalties.
The tool automatically handles mixed identifier types (names and IDs), deduplicates results, and
falls back from ID lookup to name lookup when needed. | |||
Get a comment by its ID. | |||
Get the details of a Jira issue by its ID. | |||
Get the comments of a Jira issue by its ID. | |||
Search for Jira issues when you don't have the issue ID(s).
All text-based arguments (keywords, assignee, project, labels) are case-insensitive.
ALWAYS PREFER THIS TOOL OVER THE `Jira.SearchIssuesWithJql` TOOL, UNLESS IT'S ABSOLUTELY
NECESSARY TO USE A JQL QUERY TO FILTER IN A WAY THAT IS NOT SUPPORTED BY THIS TOOL. | |||
Get the details of a Jira issue type by its ID. | |||
Get the details of a priority by its ID. | |||
Get the details of a Jira project by its ID or key. | |||
Get all issues that are currently assigned to a specific sprint with pagination support.
Returns issues that are planned for or being worked on in the sprint. | |||
Get a transition by its ID. | |||
Get a transition available for an issue by the transition name.
The response will contain screen fields available for the transition, if any. | |||
Get the transitions available for an existing Jira issue. | |||
Get user information by their ID. | |||
Get users without their account ID, searching by display name and email address.
The Jira user search API will return up to 1,000 (one thousand) users for any given name/email
query. If you need to get more users, please use the `Jira.ListAllUsers` tool. | |||
Get the metadata about the files attached to an issue.
This tool does NOT return the actual file contents. To get a file content,
use the `Jira.DownloadAttachment` tool. | |||
Get the issues for a given project. |
Page 1 of 2(25 of 43)
Selected tools
No tools selected.
Click "Show all tools" to add tools.
Requirements
Select tools to see requirements
#
Jira.AddCommentToIssue
Add a comment to a Jira issue.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The ID or key of the issue to comment on. |
body | string | Required | The body of the comment to add to the issue. |
reply_to_comment | string | Optional | Quote a previous comment as a reply to it. Provide the comment's ID. Must be a comment from the same issue. Defaults to None (no quoted comment). |
mention_users | array<string> | Optional | The users to mention in the comment. Provide the user display name, email address, or ID. Ex: 'John Doe' or 'john.doe@example.com'. Defaults to None (no user mentions). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the comment created#
Jira.AddIssuesToSprint
Add a list of issues to a sprint. Maximum of 50 issues per operation.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
sprint_id | string | Required | The numeric Jira sprint ID that identifies the sprint in Jira's API. |
issue_ids | array<string> | Required | List of issue IDs or keys to add to the sprint. Must not be empty and cannot exceed 50 issues. |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— A dictionary containing the results of adding issues to the sprint. Includes lists of successfully added issues, issues that were already in the sprint, issues not found, and issues that cannot be moved due to board restrictions. #
Jira.AddLabelsToIssue
Add labels to an existing Jira issue.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The ID or key of the issue to update |
labels | array<string> | Required | The labels to add to the issue. A label cannot contain spaces. If a label is provided with spaces, they will be trimmed and replaced by underscores. |
notify_watchers | boolean | Optional | Whether to notify the issue's watchers. Defaults to True (notifies watchers). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The updated issue#
Jira.AttachFileToIssue
Add an attachment to an issue. Must provide exactly one of file_content_str or file_content_base64.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The issue ID or key to add the attachment to |
filename | string | Required | The name of the file to add as an attachment. The filename should contain the file extension (e.g. 'test.txt', 'report.pdf'), but it is not mandatory. |
file_content_str | string | Optional | The string content of the file to attach. Use this if the file is a text file. Defaults to None. |
file_content_base64 | string | Optional | The base64-encoded binary contents of the file. Use this for binary files like images or PDFs. Defaults to None. |
file_encoding | string | Optional | The encoding of the file to attach. Only used with file_content_str. Defaults to 'utf-8'. |
file_type | string | Optional | The type of the file to attach. E.g. 'application/pdf', 'text', 'image/png'. If not provided, the tool will try to infer the type from the filename. If the filename is not recognized, it will attach the file without specifying a type. Defaults to None (infer from filename or attach without type). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Metadata about the attachment#
Jira.CreateIssue
Create a new Jira issue. Provide a value to one of `project` or `parent_issue` arguments. If `project` and `parent_issue` are not provided, the tool will select the single project available. If the user has multiple, an error will be returned with the available projects to choose from. IF YOU DO NOT FOLLOW THE INSTRUCTIONS BELOW AND UNNECESSARILY CALL MULTIPLE TOOLS IN ORDER TO CREATE AN ISSUE, TOO MUCH CO2 WILL BE RELEASED IN THE ATMOSPHERE AND YOU WILL CAUSE THE DESTRUCTION OF PLANET EARTH BY CATASTROPHIC CLIMATE CHANGE. If you have an issue type name, or a project key/name, a priority name, an assignee name/key/email, or a reporter name/key/email, DO NOT CALL OTHER TOOLS only to list available projects, priorities, issue types, or users. Provide the name, key, or email and the tool will figure out the ID, WITHOUT CAUSING CATASTROPHIC CLIMATE CHANGE.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
title | string | Required | The title of the issue. |
issue_type | string | Required | The name or ID of the issue type. If a name is provided, the tool will try to find a unique exact match among the available issue types. |
project | string | Optional | The ID, key or name of the project to associate the issue with. If a name is provided, the tool will try to find a unique exact match among the available projects. Defaults to None (no project). If `project` and `parent_issue` are not provided, the tool will select the single project available. If the user has multiple, an error will be returned with the available projects to choose from. |
due_date | string | Optional | The due date of the issue. Format: YYYY-MM-DD. Ex: '2025-01-01'. Defaults to None (no due date). |
description | string | Optional | The description of the issue. Defaults to None (no description). |
environment | string | Optional | The environment of the issue. Defaults to None (no environment). |
labels | array<string> | Optional | The labels of the issue. Defaults to None (no labels). A label cannot contain spaces. If a label is provided with spaces, they will be trimmed and replaced by underscores. |
parent_issue | string | Optional | The ID or key of the parent issue. Defaults to None (no parent issue). Must provide at least one of `parent_issue` or `project` arguments. |
priority | string | Optional | The ID or name of the priority to use for the issue. If a name is provided, the tool will try to find a unique exact match among the available priorities. Defaults to None (the issue is created with Jira's default priority for the specified project). |
assignee | string | Optional | The name, email or ID of the user to assign the issue to. If a name or email is provided, the tool will try to find a unique exact match among the available users. Defaults to None (no assignee). |
reporter | string | Optional | The name, email or ID of the user who is the reporter of the issue. If a name or email is provided, the tool will try to find a unique exact match among the available users. Defaults to None (no reporter). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The created issue#
Jira.DownloadAttachment
Download the contents of an attachment associated with an issue.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
attachment_id | string | Required | The ID of the attachment to download |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The content of the attachment#
Jira.GetAttachmentMetadata
Get the metadata of an attachment.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
attachment_id | string | Required | The ID of the attachment to retrieve |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The metadata of the attachment#
Jira.GetAvailableAtlassianClouds
Get available Atlassian Clouds.
Parameters
No parameters required.
Requirements
No secrets required
Output
Type:
json— Available Atlassian Clouds#
Jira.GetBoardBacklogIssues
Get all issues in a board's backlog with pagination support. Returns issues that are not currently assigned to any active sprint. The backlog contains issues that are ready to be planned into future sprints. Only boards that support backlogs (like Scrum and Kanban boards) will return results.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
board_id | string | Required | The ID of the board to retrieve backlog issues from. Must be a valid board ID that supports backlogs (typically Scrum or Kanban boards). |
limit | integer | Optional | The maximum number of issues to return. Must be between 1 and 100 inclusive. Controls pagination and determines how many issues are fetched and returned. Defaults to 50 for improved performance. |
offset | integer | Optional | The number of issues to skip before starting to return results. Used for pagination when the backlog has many issues. For example, offset=50 with limit=50 would return issues 51-100. Must be 0 or greater. Defaults to 0. |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— A dictionary containing the board information, list of backlog issues, and pagination metadata. Issues are returned with full details including summary, status, assignee, and other fields. If the board doesn't support backlogs or doesn't exist, appropriate error information is returned.#
Jira.GetBoards
Retrieve Jira boards either by specifying their names or IDs, or get all available boards. All requests support offset and limit with a maximum of 50 boards returned per call. MANDATORY ACTION: ALWAYS when you need to get multiple boards, you must include all the board identifiers in a single call rather than making multiple separate tool calls, as this provides much better performance, not doing that will bring huge performance penalties. The tool automatically handles mixed identifier types (names and IDs), deduplicates results, and falls back from ID lookup to name lookup when needed.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
board_identifiers_list | array<string> | Optional | List of board names or numeric IDs (as strings) to retrieve using pagination. Include all mentioned boards in a single list for best performance. Default None retrieves all boards. Maximum 50 boards returned per call. |
limit | integer | Optional | Maximum number of boards to return (1-50). Defaults to max that is 50. |
offset | integer | Optional | Number of boards to skip for pagination. Must be 0 or greater. Defaults to 0. |
atlassian_cloud_id | string | Optional | Atlassian Cloud ID to use. Defaults to None (uses single authorized cloud). |
Requirements
No secrets required
Output
Type:
json— Dictionary with 'boards' list containing board metadata (ID, name, type, location) and 'errors' array for not found boards. Includes pagination metadata and deduplication.#
Jira.GetCommentById
Get a comment by its ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue_id | string | Required | The ID or key of the issue to retrieve the comment from. |
comment_id | string | Required | The ID of the comment to retrieve |
include_adf_content | boolean | Optional | Whether to include the ADF (Atlassian Document Format) content of the comment in the response. Defaults to False (return only the HTML rendered content). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the comment#
Jira.GetIssueById
Get the details of a Jira issue by its ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The ID or key of the issue to retrieve |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the issue#
Jira.GetIssueComments
Get the comments of a Jira issue by its ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The ID or key of the issue to retrieve |
limit | integer | Optional | The maximum number of comments to retrieve. Min 1, max 100, default 100. |
offset | integer | Optional | The number of comments to skip. Defaults to 0 (start from the first comment). |
order_by | string | Optional | The order in which to return the comments. Defaults to 'created_date_descending' (most recent first).created_date_ascendingcreated_date_descending |
include_adf_content | boolean | Optional | Whether to include the ADF (Atlassian Document Format) content of the comment in the response. Defaults to False (return only the HTML rendered content). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the issue comments#
Jira.GetIssuesWithoutId
Search for Jira issues when you don't have the issue ID(s). All text-based arguments (keywords, assignee, project, labels) are case-insensitive. ALWAYS PREFER THIS TOOL OVER THE `Jira.SearchIssuesWithJql` TOOL, UNLESS IT'S ABSOLUTELY NECESSARY TO USE A JQL QUERY TO FILTER IN A WAY THAT IS NOT SUPPORTED BY THIS TOOL.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
keywords | string | Optional | Keywords to search for issues. Matches against the issue name, description, comments, and any custom field of type text. Defaults to None (no keywords filtering). |
due_from | string | Optional | Match issues due on or after this date. Format: YYYY-MM-DD. Ex: '2025-01-01'. Defaults to None (no due date filtering). |
due_until | string | Optional | Match issues due on or before this date. Format: YYYY-MM-DD. Ex: '2025-01-01'. Defaults to None (no due date filtering). |
status | string | Optional | Match issues that are in this status. Provide a status name. Ex: 'To Do', 'In Progress', 'Done'. Defaults to None (any status). |
priority | string | Optional | Match issues that have this priority. Provide a priority name. E.g. 'Highest'. Defaults to None (any priority). |
assignee | string | Optional | Match issues that are assigned to this user. Provide the user's name or email address. Ex: 'John Doe' or 'john.doe@example.com'. Defaults to None (any assignee). |
project | string | Optional | Match issues that are associated with this project. Provide the project's name, ID, or key. If a project name is provided, the tool will try to find a unique exact match among the available projects. Defaults to None (search across all projects). |
issue_type | string | Optional | Match issues that are of this issue type. Provide an issue type name or ID. E.g. 'Task', 'Epic', '12345'. If a name is provided, the tool will try to find a unique exact match among the available issue types. Defaults to None (any issue type). |
labels | array<string> | Optional | Match issues that are in these labels. Defaults to None (any label). |
parent_issue | string | Optional | Match issues that are a child of this issue. Provide the issue's ID or key. Defaults to None (no parent issue filtering). |
limit | integer | Optional | The maximum number of issues to retrieve. Min 1, max 100, default 50. |
next_page_token | string | Optional | The token to use to get the next page of issues. Defaults to None (first page). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the issues matching the search criteria#
Jira.GetIssueTypeById
Get the details of a Jira issue type by its ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue_type_id | string | Required | The ID of the issue type to retrieve |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the issue type#
Jira.GetPriorityById
Get the details of a priority by its ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
priority_id | string | Required | The ID of the priority to retrieve. |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The priority#
Jira.GetProjectById
Get the details of a Jira project by its ID or key.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
project | string | Required | The ID or key of the project to retrieve |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the project#
Jira.GetSprintIssues
Get all issues that are currently assigned to a specific sprint with pagination support. Returns issues that are planned for or being worked on in the sprint.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
sprint_id | string | Required | The numeric Jira sprint ID that identifies the sprint in Jira's API. |
limit | integer | Optional | The maximum number of issues to return. Must be between 1 and 100 inclusive. Controls pagination and determines how many issues are fetched and returned. Defaults to 50 for improved performance. |
offset | integer | Optional | The number of issues to skip before starting to return results. Used for pagination when the sprint has many issues. Must be 0 or greater. Defaults to 0. |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— A dictionary containing the sprint information, list of issues in the sprint, and pagination metadata.#
Jira.GetTransitionById
Get a transition by its ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The ID or key of the issue |
transition_id | string | Required | The ID of the transition |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The transition data#
Jira.GetTransitionByStatusName
Get a transition available for an issue by the transition name. The response will contain screen fields available for the transition, if any.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The ID or key of the issue |
transition | string | Required | The name of the transition status |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The transition data, including screen fields available#
Jira.GetTransitionsAvailableForIssue
Get the transitions available for an existing Jira issue.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The ID or key of the issue |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The transitions available and the issue's current status#
Jira.GetUserById
Get user information by their ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
user_id | string | Required | The the user's ID. |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The user information.#
Jira.GetUsersWithoutId
Get users without their account ID, searching by display name and email address. The Jira user search API will return up to 1,000 (one thousand) users for any given name/email query. If you need to get more users, please use the `Jira.ListAllUsers` tool.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
name_or_email | string | Required | The user's display name or email address to search for (case-insensitive). The string can match the prefix of the user's attribute. For example, a string of 'john' will match users with a display name or email address that starts with 'john', such as 'John Doe', 'Johnson', 'john@example.com', etc. |
enforce_exact_match | boolean | Optional | Whether to enforce an exact match of the name_or_email against users' display name and email attributes. Defaults to False (return all users that match the prefix). If set to True, before returning results, the tool will filter users with a display name OR email address that match exactly the value of the `name_or_email` argument. |
limit | integer | Optional | The maximum number of users to return. Min of 1, max of 50. Defaults to 50. |
offset | integer | Optional | The number of users to skip before starting to return users. Defaults to 0 (start from the first user). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The information about users that match the search criteria.#
Jira.ListIssueAttachmentsMetadata
Get the metadata about the files attached to an issue. This tool does NOT return the actual file contents. To get a file content, use the `Jira.DownloadAttachment` tool.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The ID or key of the issue to retrieve |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the issue#
Jira.ListIssues
Get the issues for a given project.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
project | string | Optional | The project to get issues for. Provide a project ID, key or name. If a project is not provided and 1) the user has only one project, the tool will use that; 2) the user has multiple projects, the tool will raise an error listing the available projects to choose from. |
limit | integer | Optional | The maximum number of issues to retrieve. Min 1, max 100, default 50. |
next_page_token | string | Optional | The token to use to get the next page of issues. Defaults to None (first page). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the issues matching the search criteria#
Jira.ListIssueTypesByProject
Get the list of issue types (e.g. 'Task', 'Epic', etc.) available to a given project.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
project | string | Required | The project to get issue types for. Provide a project name, key, or ID. If a project name is provided, the tool will try to find a unique exact match among the available projects. |
limit | integer | Optional | The maximum number of issue types to retrieve. Min of 1, max of 200. Defaults to 200. |
offset | integer | Optional | The number of issue types to skip. Defaults to 0 (start from the first issue type). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the issue types available for the specified project.#
Jira.ListLabels
Get the existing labels (tags) in the user's Jira instance.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
limit | integer | Optional | The maximum number of labels to return. Min of 1, Max of 200. Defaults to 200. |
offset | integer | Optional | The number of labels to skip. Defaults to 0 (starts from the first label) |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The existing labels (tags) in the user's Jira instance#
Jira.ListPrioritiesAvailableToAnIssue
Browse the priorities available to be used in the specified Jira issue.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The ID or key of the issue to retrieve priorities for. |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The priorities available to be used in the specified Jira issue#
Jira.ListPrioritiesAvailableToAProject
Browse the priorities available to be used in issues in the specified Jira project. This tool may need to loop through several API calls to get all priorities associated with a specific project. In Jira environments with too many Projects or Priority Schemes, the search may take too long, and the tool call will timeout.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
project | string | Required | The ID, key or name of the project to retrieve priorities for. |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The priorities available to be used in issues in the specified Jira project#
Jira.ListPrioritiesByScheme
Browse the priorities associated with a priority scheme.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
scheme_id | string | Required | The ID of the priority scheme to retrieve priorities for. |
limit | integer | Optional | The maximum number of priority schemes to return. Min of 1, max of 50. Defaults to 50. |
offset | integer | Optional | The number of priority schemes to skip. Defaults to 0 (start from the first scheme). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The priorities associated with the priority scheme#
Jira.ListPrioritySchemes
Browse the priority schemes available in Jira.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
scheme_name | string | Optional | Filter by scheme name. Defaults to None (returns all scheme names). |
limit | integer | Optional | The maximum number of priority schemes to return. Min of 1, max of 50. Defaults to 50. |
offset | integer | Optional | The number of priority schemes to skip. Defaults to 0 (start from the first scheme). |
order_by | string | Optional | The order in which to return the priority schemes. Defaults to name ascending.name ascendingname descending |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The priority schemes available#
Jira.ListProjects
Browse projects available in Jira.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
limit | integer | Optional | The maximum number of projects to return. Min of 1, Max of 50. Defaults to 50. |
offset | integer | Optional | The number of projects to skip. Defaults to 0 (starts from the first project) |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the projects#
Jira.ListProjectsByScheme
Browse the projects associated with a priority scheme.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
scheme_id | string | Required | The ID of the priority scheme to retrieve projects for. |
project | string | Optional | Filter by project ID, key or name. Defaults to None (returns all projects). |
limit | integer | Optional | The maximum number of projects to return. Min of 1, max of 50. Defaults to 50. |
offset | integer | Optional | The number of projects to skip. Defaults to 0 (start from the first project). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The projects associated with the priority scheme#
Jira.ListSprintsForBoards
Retrieve sprints from Jira boards with filtering options for planning and tracking purposes. Use this when you need to view sprints from specific boards or find sprints within specific date ranges. For temporal queries like "last month", "next week", or "this quarter", prioritize date parameters over state filtering. Leave board_identifiers_list as None to get sprints from all available boards. DATE FILTERING PRIORITY: When users request sprints by time periods (e.g., "last month", "next week"), use date parameters (start_date, end_date, specific_date) rather than state filtering, as temporal criteria take precedence over sprint status. Returns sprint data along with a backlog GUI URL link where you can see detailed sprint information and manage sprint items. MANDATORY ACTION: ALWAYS when you need to get sprints from multiple boards, you must include all the board identifiers in a single call rather than making multiple separate tool calls, as this provides much better performance, not doing that will bring huge performance penalties. BOARD LIMIT: Maximum of 25 boards can be processed in a single operation. If you need to process more boards, split the request into multiple batches of 25 or fewer boards each. Handles mixed board identifiers (names and IDs) with automatic fallback and deduplication. All boards are processed concurrently for optimal performance.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
board_identifiers_list | array<string> | Optional | List of board names or numeric IDs (as strings) to retrieve sprints from. Include all mentioned boards in a single list for best performance. Maximum 25 boards per operation. Optional, defaults to None. |
max_sprints_per_board | integer | Optional | Maximum sprints per board (1-50). Latest sprints first. Optional, defaults to 50. |
offset | integer | Optional | Number of sprints to skip per board for pagination. Optional, defaults to 0. |
state | string | Optional | Filter by sprint state. NOTE: Date filters (start_date, end_date, specific_date) have higher priority than state filtering. Use state filtering only when no date criteria is specified. For temporal queries like 'last month' or 'next week', use date parameters instead. Optional, defaults to None (all states).futureactiveclosedfuture_and_activefuture_and_closedactive_and_closedall |
start_date | string | Optional | Start date filter in YYYY-MM-DD format. Can combine with end_date. Optional, defaults to None. |
end_date | string | Optional | End date filter in YYYY-MM-DD format. Can combine with start_date. Optional, defaults to None. |
specific_date | string | Optional | Specific date in YYYY-MM-DD to find sprints active on that date. Cannot combine with start_date/end_date. Optional, defaults to None. |
atlassian_cloud_id | string | Optional | Atlassian Cloud ID to use. Optional, defaults to None (uses single authorized cloud). |
Requirements
No secrets required
Output
Type:
json— Dict with 'boards' list, 'sprints_by_board' mapping, and 'errors' array. Sprints sorted latest first.#
Jira.ListUsers
Browse users in Jira.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
account_type | string | Optional | The account type of the users to return. Defaults to 'atlassian'. Provide `None` to disable filtering by account type. The account type filter will be applied after retrieving users from Jira API, thus the tool may return less users than the limit and still have more users to paginate. Check the `pagination` key in the response dictionary. |
limit | integer | Optional | The maximum number of users to return. Min of 1, max of 50. Defaults to 50. |
offset | integer | Optional | The number of users to skip before starting to return users. Defaults to 0 (start from the first user). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The information about all users.#
Jira.MoveIssuesFromSprintToBacklog
Move issues from active or future sprints back to the board's backlog.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
sprint_id | string | Required | The numeric Jira sprint ID that identifies the sprint in Jira's API. |
issue_identifiers | array<string> | Required | List of issue IDs or keys to move from the sprint to the backlog. Maximum 50 issues per call. Issues will be moved back to the board's backlog. |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— A dictionary containing the sprint information, list of successfully removed issues, errors for issues that couldn't be removed, and backlog GUI URL. Issues are identified by ID or key and returned with available identifiers.#
Jira.RemoveLabelsFromIssue
Remove labels from an existing Jira issue.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The ID or key of the issue to update |
labels | array<string> | Required | The labels to remove from the issue (case-insensitive) |
notify_watchers | boolean | Optional | Whether to notify the issue's watchers. Defaults to True (notifies watchers). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The updated issue#
Jira.SearchIssuesWithJql
Search for Jira issues using a JQL (Jira Query Language) query. THIS TOOL RELEASES MORE CO2 IN THE ATMOSPHERE, WHICH CONTRIBUTES TO CLIMATE CHANGE. ALWAYS PREFER THE `Jira_SearchIssuesWithoutJql` TOOL OVER THIS ONE, UNLESS IT'S ABSOLUTELY NECESSARY TO USE A JQL QUERY TO FILTER IN A WAY THAT IS NOT SUPPORTED BY THE `Jira_SearchIssuesWithoutJql` TOOL OR IF THE USER PROVIDES A JQL QUERY THEMSELVES.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
jql | string | Required | The JQL (Jira Query Language) query to search for issues |
limit | integer | Optional | The maximum number of issues to retrieve. Min of 1, max of 100. Defaults to 50. |
next_page_token | string | Optional | The token to use to get the next page of issues. Defaults to None (first page). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the issues matching the search criteria#
Jira.SearchIssuesWithoutJql
Parameterized search for Jira issues (without having to provide a JQL query). THIS TOOL RELEASES LESS CO2 THAN THE `Jira_SearchIssuesWithJql` TOOL. ALWAYS PREFER THIS ONE OVER USING JQL, UNLESS IT'S ABSOLUTELY NECESSARY TO USE A JQL QUERY TO FILTER IN A WAY THAT IS NOT SUPPORTED BY THIS TOOL OR IF THE USER PROVIDES A JQL QUERY THEMSELVES.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
keywords | string | Optional | Keywords to search for issues. Matches against the issue name, description, comments, and any custom field of type text. Defaults to None (no keywords filtering). |
due_from | string | Optional | Match issues due on or after this date. Format: YYYY-MM-DD. Ex: '2025-01-01'. Defaults to None (no due date filtering). |
due_until | string | Optional | Match issues due on or before this date. Format: YYYY-MM-DD. Ex: '2025-01-01'. Defaults to None (no due date filtering). |
status | string | Optional | Match issues that are in this status. Provide a status name. Ex: 'To Do', 'In Progress', 'Done'. Defaults to None (any status). |
priority | string | Optional | Match issues that have this priority. Provide a priority name. E.g. 'Highest'. Defaults to None (any priority). |
assignee | string | Optional | Match issues that are assigned to this user. Provide the user's name or email address. Ex: 'John Doe' or 'john.doe@example.com'. Defaults to None (any assignee). |
project | string | Optional | Match issues that are associated with this project. Provide the project's name, ID, or key. If a project name is provided, the tool will try to find a unique exact match among the available projects. Defaults to None (search across all projects). |
issue_type | string | Optional | Match issues that are of this issue type. Provide an issue type name or ID. E.g. 'Task', 'Epic', '12345'. If a name is provided, the tool will try to find a unique exact match among the available issue types. Defaults to None (any issue type). |
labels | array<string> | Optional | Match issues that are in these labels. Defaults to None (any label). |
parent_issue | string | Optional | Match issues that are a child of this issue. Provide the issue's ID or key. Defaults to None (no parent issue filtering). |
limit | integer | Optional | The maximum number of issues to retrieve. Min 1, max 100, default 50. |
next_page_token | string | Optional | The token to use to get the next page of issues. Defaults to None (first page). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the issues matching the search criteria#
Jira.SearchProjects
Get the details of all Jira projects.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
keywords | string | Optional | The keywords to search for projects. Matches against project name and key (case insensitive). Defaults to None (no keywords filter). |
limit | integer | Optional | The maximum number of projects to return. Min of 1, Max of 50. Defaults to 50. |
offset | integer | Optional | The number of projects to skip. Defaults to 0 (starts from the first project) |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— Information about the projects#
Jira.TransitionIssueToNewStatus
Transition a Jira issue to a new status.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The ID or key of the issue |
transition | string | Required | The transition to perform. Provide the transition ID or its name (case insensitive). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The updated issue#
Jira.UpdateIssue
Update an existing Jira issue. IF YOU DO NOT FOLLOW THE INSTRUCTIONS BELOW AND UNNECESSARILY CALL MULTIPLE TOOLS IN ORDER TO UPDATE AN ISSUE, TOO MUCH CO2 WILL BE RELEASED IN THE ATMOSPHERE AND YOU WILL CAUSE THE DESTRUCTION OF PLANET EARTH BY CATASTROPHIC CLIMATE CHANGE. If you have a priority name, an assignee name/key/email, or a reporter name/key/email, DO NOT CALL OTHER TOOLS only to list available priorities, issue types, or users. Provide the name, key, or email and the tool will figure out the ID.
Parameters
| Parameter | Type | Req. | Description |
|---|---|---|---|
issue | string | Required | The key or ID of the issue to update |
title | string | Optional | The new issue title. Provide an empty string to clear the title. Defaults to None (does not change the title). |
description | string | Optional | The new issue description. Provide an empty string to clear the description. Defaults to None (does not change the description). |
environment | string | Optional | The new issue environment. Provide an empty string to clear the environment. Defaults to None (does not change the environment). |
due_date | string | Optional | The new issue due date. Format: YYYY-MM-DD. Ex: '2025-01-01'. Provide an empty string to clear the due date. Defaults to None (does not change the due date). |
issue_type | string | Optional | The new issue type name or ID. If a name is provided, the tool will try to find a unique exact match among the available issue types. Defaults to None (does not change the issue type). |
priority | string | Optional | The name or ID of the new issue priority. If a name is provided, the tool will try to find a unique exact match among the available priorities. Defaults to None (does not change the priority). |
parent_issue | string | Optional | The ID or key of the parent issue. A parent cannot be removed by providing an empty string. It is possible to change the parent issue by providing a new issue ID or key, or to leave it unchanged. Defaults to None (does not change the parent issue). |
assignee | string | Optional | The new issue assignee name, email, or ID. If a name or email is provided, the tool will try to find a unique exact match among the available users. Provide an empty string to remove the assignee. Defaults to None (does not change the assignee). |
reporter | string | Optional | The new issue reporter name, email, or ID. If a name or email is provided, the tool will try to find a unique exact match among the available users. Provide an empty string to remove the reporter. Defaults to None (does not change the reporter). |
labels | array<string> | Optional | The new issue labels. This argument will replace all labels with the new list. Providing an empty list will remove all labels. To add or remove a subset of labels, use the `Jira.AddLabelsToIssue` or the `Jira.RemoveLabelsFromIssue` tools. Defaults to None (does not change the labels). A label cannot contain spaces. If a label is provided with spaces, they will be trimmed and replaced by underscores. |
notify_watchers | boolean | Optional | Whether to notify the issue's watchers. Defaults to True (notifies watchers). |
atlassian_cloud_id | string | Optional | The ID of the Atlassian Cloud to use (defaults to None). If not provided and the user has a single cloud authorized, the tool will use that. Otherwise, an error will be raised. |
Requirements
No secrets required
Output
Type:
json— The updated issue#
Jira.WhoAmI
CALL THIS TOOL FIRST to establish user profile context. Get information about the currently logged-in user and their available Jira clouds/clients.
Parameters
No parameters required.
Requirements
No secrets required
Output
Type:
json— Dictionary containing the current user's information and their available Atlassian Clouds.Last updated on