jira-mcp-server

bulk_transition_issues

Transition multiple Jira issues to a new status in one operation. Specify issue keys and a transition ID to apply the workflow change.

Instructions

Transition multiple issues to a new status

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issueKeys": "<issueKeys>",
      "transitionId": "<transitionId>"
    },
    "name": "bulk_transition_issues"
  }
}

Input Schema

Name	Required	Description	Default
`issueKeys`	Yes
`transitionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

B3.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but does not disclose potential side effects, atomicity, partial failure behavior, permissions required, or how the transition interacts with workflows. For a bulk mutation tool, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words, achieving high conciseness. However, it is slightly under-specified, but for a simple tool this length is acceptable. It is appropriately front-loaded with the action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has only two parameters and no output schema, but the description is too sparse. It omits critical operational context such as how to obtain transitionId, whether the operation is atomic or partial, and what happens on failure. This makes it incomplete for safe and correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description gives minimal semantic clues: 'multiple issues' maps to issueKeys, and 'new status' loosely maps to transitionId. However, it does not explain that issueKeys is an array of issue keys or that transitionId should come from get_transitions. With 0% schema description coverage, the description fails to adequately compensate for the undocumented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool transitions multiple issues to a new status, using a specific verb ('transition') and resource ('multiple issues'). It distinguishes itself from the sibling tool 'transition_issue' by emphasizing the bulk nature, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'multiple issues' implies the tool is intended for batch operations, providing clear context for when to use it. However, it does not explicitly mention alternatives like 'transition_issue' for single-issue transitions, so it lacks explicit exclusions or when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.