Skip to main content
Glama
cosmix

JIRA MCP Server

by cosmix

transition_issue

Change JIRA issue status by performing transitions with optional comments to track workflow progress.

Instructions

Change the status of a JIRA issue by performing a transition

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe key of the issue to transition
transitionIdYesThe ID of the transition to perform
commentNoOptional comment to add with the transition

Implementation Reference

  • The core handler function that executes the Jira API transition request, including optional comment in ADF format.
    async transitionIssue(
      issueKey: string,
      transitionId: string,
      comment?: string
    ): Promise<void> {
      const payload: any = {
        transition: { id: transitionId },
      };
    
      if (comment) {
        payload.update = {
          comment: [
            {
              add: {
                body: {
                  type: "doc",
                  version: 1,
                  content: [
                    {
                      type: "paragraph",
                      content: [
                        {
                          type: "text",
                          text: comment,
                        },
                      ],
                    },
                  ],
                },
              },
            },
          ],
        };
      }
    
      await this.fetchJson(`/rest/api/3/issue/${issueKey}/transitions`, {
        method: "POST",
        body: JSON.stringify(payload),
      });
    }
  • Input schema definition for the transition_issue tool, specifying parameters and validation.
    inputSchema: {
      type: "object",
      properties: {
        issueKey: {
          type: "string",
          description: "The key of the issue to transition",
        },
        transitionId: {
          type: "string",
          description: "The ID of the transition to perform",
        },
        comment: {
          type: "string",
          description: "Optional comment to add with the transition",
        },
      },
      required: ["issueKey", "transitionId"],
      additionalProperties: false,
    },
  • src/index.ts:200-222 (registration)
    Tool registration in the listTools response, including name, description, and schema.
      name: "transition_issue",
      description:
        "Change the status of a JIRA issue by performing a transition",
      inputSchema: {
        type: "object",
        properties: {
          issueKey: {
            type: "string",
            description: "The key of the issue to transition",
          },
          transitionId: {
            type: "string",
            description: "The ID of the transition to perform",
          },
          comment: {
            type: "string",
            description: "Optional comment to add with the transition",
          },
        },
        required: ["issueKey", "transitionId"],
        additionalProperties: false,
      },
    },
  • MCP tool dispatch handler that validates parameters and delegates to JiraApiService.transitionIssue.
    case "transition_issue": {
      if (
        !args.issueKey ||
        typeof args.issueKey !== "string" ||
        !args.transitionId ||
        typeof args.transitionId !== "string"
      ) {
        throw new McpError(
          ErrorCode.InvalidParams,
          "issueKey and transitionId are required",
        );
      }
      await this.jiraApi.transitionIssue(
        args.issueKey,
        args.transitionId,
        args.comment as string | undefined,
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              {
                message: `Issue ${args.issueKey} transitioned successfully${args.comment ? " with comment" : ""}`,
              },
              null,
              2,
            ),
          },
        ],
      };
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like required permissions, whether the transition is reversible, side effects (e.g., notifications), rate limits, or what happens on success/failure. 'Change the status' implies mutation but lacks depth.

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 with zero waste. It's front-loaded with the core purpose and appropriately sized for the tool's complexity.

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

Completeness3/5

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

Given a mutation tool with no annotations and no output schema, the description is minimally adequate but incomplete. It covers the basic purpose but lacks crucial context like behavioral details, usage guidelines, and output expectations, leaving gaps for an AI agent.

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%, so the schema fully documents parameters (issueKey, transitionId, comment). The description adds no meaning beyond this, as it doesn't explain parameter relationships (e.g., transitionId must be valid for the issue) or usage context.

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 ('Change the status') and resource ('a JIRA issue') with the specific mechanism ('by performing a transition'). It distinguishes from siblings like 'update_issue' which might handle other fields, but doesn't explicitly contrast with 'get_transitions' which likely provides available transitions.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing to know valid transition IDs from 'get_transitions'), exclusions, or contextual triggers for status changes.

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/cosmix/jira-mcp'

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