Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Transition issue

jira_transition_issue

Move a Jira issue through its workflow by specifying a transition ID, transition name, or target status; optionally add a comment during the transition.

Instructions

Move an issue through its workflow. 'transition' may be a transition id, a transition name or the target status name.

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": {
      "issue": "<issue>",
      "transition": "<transition>"
    },
    "name": "jira_transition_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueYesIssue key ('ABC-123'), instance-prefixed key ('work:ABC-123') or full browse URL ('https://acme.atlassian.net/browse/ABC-123').
commentNoOptional comment added with the transition.
instanceNoJira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists.
transitionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so safety profile and external-dependency status are covered without the description's help. The description adds nothing further about failure behavior for an invalid transition, whether the transition is reversible, or how the optional comment interacts with the transition atomically; for a mutation tool with no output schema, some of that context would be worth stating.

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

Conciseness5/5

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

Two short sentences, zero filler, with the operation stated first and the ambiguous parameter explained second. Nothing could be removed without losing information.

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 four-parameter mutation tool, the definition covers the operation and disambiguates the one opaque parameter, and the annotations plus schema carry the instance-routing and issue-key details. What remains missing is a pointer to jira_get_transitions for discovering valid transitions and any note on how errors surface, which is the main completeness gap.

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

Parameters4/5

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

Schema coverage is 75%, and the uncovered parameter is exactly 'transition', which the description uniquely explains as accepting a transition id, a transition name, or a target status name. That is real added meaning an agent could not get from the schema, since the schema lists 'transition' with no description at all.

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

Purpose4/5

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

"Move an issue through its workflow" gives a specific verb and resource that an agent can match to the workflow-transition concept, and the clarification of what 'transition' means reinforces the operation. It stops short of distinguishing itself from near siblings such as jira_update_issue or jira_get_transitions, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

The purpose sentence implies the usage context (an issue needs to change workflow state), but there is no explicit when-to-use or when-not-to-use guidance. Critically, it never points to jira_get_transitions as the way to discover valid transition ids or names, even though the description acknowledges the agent must supply one of those forms.

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