Skip to main content
Glama

jira_transition_issue

Change a Jira issue's status to move it through workflow stages like In Progress or Done.

Instructions

Transition a Jira issue to a different status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_keyYesIssue key (e.g., PROJ-123)
statusYesTarget status (e.g., In Progress, Done)

Implementation Reference

  • Executes the tool logic: retrieves available transitions for the issue, finds the matching one for the target status, performs the transition using the Jira client, and returns success or available statuses message.
    async def _transition_issue(self, arguments: dict) -> List[TextContent]:
        """Transition an issue to a different status"""
        issue_key = arguments["issue_key"]
        target_status = arguments["status"]
        
        # Get available transitions
        transitions = self.jira_client.get_issue_transitions(issue_key)
        
        # Find the transition that matches the target status
        transition_id = None
        for transition in transitions["transitions"]:
            if transition["to"]["name"].lower() == target_status.lower():
                transition_id = transition["id"]
                break
        
        if not transition_id:
            available_statuses = [t["to"]["name"] for t in transitions["transitions"]]
            return [TextContent(
                type="text",
                text=f"Cannot transition to '{target_status}'. Available statuses: {', '.join(available_statuses)}"
            )]
        
        self.jira_client.set_issue_status(issue_key, transition_id)
        
        return [TextContent(
            type="text",
            text=f"Transitioned issue {issue_key} to status: {target_status}"
        )]
  • Registers the 'jira_transition_issue' tool with the MCP server, including its description and input schema defining required parameters: issue_key and status.
    Tool(
        name="jira_transition_issue",
        description="Transition a Jira issue to a different status",
        inputSchema={
            "type": "object",
            "properties": {
                "issue_key": {
                    "type": "string",
                    "description": "Issue key (e.g., PROJ-123)"
                },
                "status": {
                    "type": "string",
                    "description": "Target status (e.g., In Progress, Done)"
                }
            },
            "required": ["issue_key", "status"]
        }
    ),
  • Dispatch logic in the call_tool handler that routes calls to 'jira_transition_issue' to the _transition_issue method.
    elif name == "jira_transition_issue":
        return await self._transition_issue(arguments)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Transition') but doesn't explain what this entails—e.g., whether it requires specific permissions, if it's reversible, what happens to workflow steps, or if there are side effects like notifications. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's front-loaded with the core action, making it easy to parse and understand quickly.

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?

Given the complexity of a mutation tool (changing issue status in Jira) with no annotations and no output schema, the description is incomplete. It lacks crucial context like permission requirements, workflow implications, error conditions, or what the tool returns. This leaves significant gaps for an AI agent to use it effectively.

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?

The schema description coverage is 100%, with both parameters ('issue_key' and 'status') clearly documented in the input schema. The description adds no additional meaning beyond what the schema provides, such as examples of valid statuses or constraints on issue keys. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the verb ('Transition') and resource ('a Jira issue') with the specific action ('to a different status'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'jira_update_issue' which might also change status, but the verb 'transition' is specific enough for basic differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'jira_update_issue' (which might handle status changes differently) or 'jira_get_issue' (for checking current status). There's no mention of prerequisites, such as needing valid issue keys or available status transitions, leaving usage context entirely implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/katsuhirohonda/jira-confluence-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server