Skip to main content
Glama

Get Jira issue transitions

get_transitions
Read-only

Retrieve available Jira issue transitions, including transition IDs, names, target statuses, and screen fields with required flags and allowed values.

Instructions

Get available transitions for a Jira issue. Returns transition IDs, names, target statuses, and screen fields with required flags and allowed values.

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_key": "<issue_key>"
    },
    "name": "get_transitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
config_idNoJira instance to use, from list_configs. Omit for the default.
issue_keyYesIssue key, e.g. ONE-123.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds valuable return-shape detail (transition IDs, target statuses, screen fields with required flags and allowed values), which is real context beyond the annotations, but it omits that available transitions vary by user permissions and current issue status.

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, front-loading the purpose before the return-value detail. Every clause carries information; there is no filler or redundancy.

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?

With no output schema, the description correctly compensates by summarizing the response contents, which is the most important thing an agent needs here. It stops short of noting that results depend on workflow state and permissions, or pointing to transition_issue as the follow-up action.

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 description coverage is 100% and both parameters (config_id, issue_key) are documented in the schema, including the example key format. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource ('Get available transitions for a Jira issue') and then enumerates what the result contains. It implicitly separates itself from transition_issue (read available transitions vs. apply one), but never names or contrasts a sibling explicitly.

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?

Usage is only implied: returning transition IDs and screen fields suggests you call this before transition_issue to discover valid IDs and required inputs. There is no explicit when-to-use statement, no precondition (e.g. permissions or current workflow status), and no stated alternative.

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