Loading ToolBench
Create and manage issues, projects, and sprints in Jira.
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.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-03-06 | A+ | 96 | - | v1 |
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.
Get the details of a Jira issue type 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 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 list of issue types (e.g. 'Task', 'Epic', etc.) available to a given project.
Get the issues for a given project.
Get the existing labels (tags) in the user's Jira instance.
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.
Browse the priorities available to be used in the specified Jira issue.
Browse the priorities associated with a priority scheme.
Browse the priority schemes available in Jira.
Browse projects available in Jira.
Browse the projects associated with a priority scheme.
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.
Browse users in Jira.
Move issues from active or future sprints back to the board's backlog.
Remove labels from an existing Jira issue.
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.
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.
Get the details of all Jira projects.
Transition a Jira issue to a new status.
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.
CALL THIS TOOL FIRST to establish user profile context. Get information about the currently logged-in user and their available Jira clouds/clients.