Skip to main content
Glama
proprock

jira-mini-mcp

by proprock
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

transition_issue

Destructive

Move a Jira issue to another workflow state by specifying the transition name or target status; optionally add a Markdown comment in the same call.

Instructions

Move an issue through its workflow. to is a transition name or the name of the status to reach, matched ignoring case and surrounding space. A transition's name often differs from the status it leads to (a transition called 'In Progress' can produce status 'In Development'), and two transitions can reach one status, so prefer the transition name; if nothing matches, the error lists every available transition and its resulting status. comment is Markdown and is posted in the same call as the move. Changes issue state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
commentNo
issue_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "transition_issueDictOutput",
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark it as non-read-only and destructive; the description adds valuable detail: it changes issue state, posts the comment in the same call, explains matching behavior, and describes the error response. This goes well beyond what annotations alone convey.

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?

Every sentence adds value: purpose, parameter semantics, matching nuance, error handling, comment behavior, and state change. It is front-loaded with the main action and flows logically, with no wasted words.

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

Completeness5/5

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

For a state-changing tool with no output schema, the description covers all critical aspects: how to specify the target, what happens on no match, the comment being posted in the same call, and the state change. The destructive nature is already in annotations, so nothing essential is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must explain parameters. It thoroughly explains 'to' (transition name/status, matching rules, error behavior) and 'comment' (Markdown, posted in same call). Issue_key is self-explanatory, but the description compensates fully for the schema's lack of descriptions.

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 states 'Move an issue through its workflow' – a clear verb+resource. It further explains the 'to' parameter and that it changes issue state, making the purpose unmistakable and distinct from siblings like add_comment or 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 Guidelines4/5

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

Provides explicit guidance on how to specify the target: prefer transition name over status, matching is case-insensitive and trims spaces, and the error fallback lists all transitions. It doesn't explicitly name alternative tools, but the usage context is clear and well-specified.

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

Deploy Server

Other Tools