Skip to main content
Glama
akhilthomas236

MCP Jira & Confluence Server

transition-jira-issue

Move a Jira issue to a new status by providing the issue key and transition ID.

Instructions

Transition a Jira issue to a new status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_keyYes
transition_idYes

Implementation Reference

  • Registration and schema definition for the transition-jira-issue tool, listing issue_key and transition_id as required parameters.
    types.Tool(
        name="transition-jira-issue",
        description="Transition a Jira issue to a new status",
        inputSchema={
            "type": "object",
            "properties": {
                "issue_key": {"type": "string"},
                "transition_id": {"type": "string"},
            },
            "required": ["issue_key", "transition_id"],
        },
  • Handler for transition-jira-issue tool execution. Validates arguments, calls jira_client.transition_issue(), then fetches the issue to display the new status.
    elif name == "transition-jira-issue":
        issue_key = arguments.get("issue_key")
        transition_id = arguments.get("transition_id")
        
        if not issue_key or not transition_id:
            raise ValueError("Missing required arguments: issue_key and transition_id")
            
        await jira_client.transition_issue(
            issue_key=issue_key,
            transition_id=transition_id
        )
        
        # Get the issue to see the new status
        issue = await jira_client.get_issue(issue_key)
        new_status = issue["fields"]["status"]["name"] if "status" in issue["fields"] else "Unknown"
        
        return [
            types.TextContent(
                type="text",
                text=f"Transitioned Jira issue {issue_key} to status: {new_status}",
            ),
            types.EmbeddedResource(
                type="resource",
                resource=types.TextResourceContents(
                    uri=AnyUrl(build_jira_uri(issue_key)),
                    text=f"Transitioned Jira issue {issue_key} to status: {new_status}",
                    mimeType="text/markdown"
                )
            )
        ]
  • JiraClient helper method that sends a POST request to the Jira API to transition an issue to a new status using the transition ID.
    async def transition_issue(self, issue_key: str, transition_id: str) -> Dict[str, Any]:
        """Transition an issue to a new status."""
        data = {
            "transition": {"id": transition_id}
        }
        return await self.post(f"issue/{issue_key}/transitions", data)
  • JiraClient helper method to retrieve available transitions for an issue, which can be used to discover valid transition IDs.
    async def get_transitions(self, issue_key: str) -> Dict[str, Any]:
        """Get available transitions for an issue."""
        return await self.get(f"issue/{issue_key}/transitions")
  • Data model representing a Jira transition with id, name, and to_status fields.
    class JiraTransition:
        """Representation of a Jira transition."""
        id: str
        name: str
        to_status: str
Behavior2/5

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

Description is minimal and does not disclose side effects, validation rules, idempotency, or error states. Since no annotations are provided, the description fails to compensate with behavioral details.

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

Conciseness3/5

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

The description is a single sentence, but it is too brief and lacks details. Conciseness is good, but structure is minimal and does not earn its place with useful information.

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?

With no output schema and no annotations, the description should provide contextual completeness about return values, error handling, or prerequisite states. It does not, leaving the agent underinformed.

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

Parameters2/5

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

The description does not explain the parameters 'issue_key' and 'transition_id'. It mentions 'new status' but does not connect that to the transition_id parameter. Schema coverage is 0%, and the description adds no parameter meaning.

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 action (transition) and resource (a Jira issue) but does not specify that the transition is identified by a transition ID, which is slightly ambiguous. It is distinct from sibling tools like create or comment.

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?

No guidance on when to use this tool versus alternatives like create-jira-issue or comment-jira-issue. No context about prerequisites or when transitions are applicable.

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/akhilthomas236/mcp-jira-confluence-sse'

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