Skip to main content
Glama

jira_transition_issue

Change a Jira issue's workflow status by applying a valid transition ID from jira_get_transitions, with an optional comment explaining the status change.

Instructions

Move a Jira issue to a different workflow status (e.g., "To Do" → "In Progress" → "Done"). This is how you change an issue's status. You MUST first call jira_get_transitions to get the valid transition ID for the desired status change. Optionally include a comment explaining the transition.

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": {
      "issueKey": "<issueKey>",
      "transitionId": "<transitionId>"
    },
    "name": "jira_transition_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoOptional comment explaining why the status is changing
issueKeyYesIssue key to transition (e.g., KP-123)
transitionIdYesTransition ID from jira_get_transitions (e.g., "21", "31")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it usefully discloses the mandatory two-step workflow and that commenting is optional, but says nothing about permission requirements, failure modes for an invalid/stale transition ID, or side effects such as notifications and workflow post-functions.

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?

Front-loaded with the action and the hard prerequisite, and every sentence is short and functional; the clause 'This is how you change an issue's status' mildly repeats the opening sentence but does aid sibling disambiguation.

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

Completeness4/5

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

For a simple three-parameter mutation with full schema coverage, the description covers the action, the prerequisite lookup, and the optional comment; only a note on what happens with an invalid transition (and the absence of any output schema) leaves a small gap.

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

Parameters3/5

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

Schema coverage is 100% and the schema already describes issueKey format and that transitionId comes from jira_get_transitions, so the description largely restates structured data; it adds only the minor clarification that the comment explains why the status is changing.

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?

States a specific verb and resource ('Move a Jira issue to a different workflow status') and reinforces scope with 'This is how you change an issue's status', which separates it from field-editing siblings like jira_update_issue.

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

Usage Guidelines5/5

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

Explicitly names the prerequisite tool and the ordering constraint ('You MUST first call jira_get_transitions to get the valid transition ID'), so an agent cannot attempt the call without the required lookup step.

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