Skip to main content
Glama
hackdonalds

JIRA MCP Server

by hackdonalds

Transition JIRA Issue

jira_transition_issue

Change the status of a JIRA issue by applying a specific transition, with an optional comment.

Instructions

Transition an issue to a new status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe JIRA issue key
transitionIdYesThe transition ID
commentNoOptional comment for the transition

Implementation Reference

  • MCP tool handler that invokes the JiraClient to transition the issue and formats the response.
    async ({ issueKey, transitionId, comment }) => {
      logger.info('Transitioning JIRA issue', { issueKey, transitionId });
      try {
        await jiraClient.transitionIssue(issueKey, transitionId, comment);
        logger.info('Successfully transitioned issue', { 
          issueKey,
          transitionId
        });
        return {
          content: [{
            type: 'text',
            text: `Issue ${issueKey} transitioned successfully`
          }]
        };
      } catch (error) {
        logger.error('Failed to transition issue', { issueKey, transitionId, error: error.message });
        throw error;
      }
    }
  • Input schema using Zod for validating tool parameters.
    inputSchema: {
      issueKey: z.string().describe('The JIRA issue key'),
      transitionId: z.string().describe('The transition ID'),
      comment: z.string().optional().describe('Optional comment for the transition')
    }
  • server.js:340-370 (registration)
    Registration of the 'jira_transition_issue' tool with the MCP server, including schema and handler.
    server.registerTool(
      'jira_transition_issue',
      {
        title: 'Transition JIRA Issue',
        description: 'Transition an issue to a new status',
        inputSchema: {
          issueKey: z.string().describe('The JIRA issue key'),
          transitionId: z.string().describe('The transition ID'),
          comment: z.string().optional().describe('Optional comment for the transition')
        }
      },
      async ({ issueKey, transitionId, comment }) => {
        logger.info('Transitioning JIRA issue', { issueKey, transitionId });
        try {
          await jiraClient.transitionIssue(issueKey, transitionId, comment);
          logger.info('Successfully transitioned issue', { 
            issueKey,
            transitionId
          });
          return {
            content: [{
              type: 'text',
              text: `Issue ${issueKey} transitioned successfully`
            }]
          };
        } catch (error) {
          logger.error('Failed to transition issue', { issueKey, transitionId, error: error.message });
          throw error;
        }
      }
    );
  • JiraClient helper method that makes the actual JIRA REST API call to transition the issue.
    async transitionIssue(issueKey, transitionId, comment = null) {
      logger.info('Transitioning JIRA issue', { issueKey, transitionId, comment });
      const body = { transition: { id: transitionId } };
      if (comment) {
        body.update = { comment: [{ add: { body: comment } }] };
      }
      return await this.makeRequest(`issue/${issueKey}/transitions`, {
        method: 'POST',
        body: JSON.stringify(body)
      });
    }
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 cover critical aspects like required permissions, whether the transition is reversible, rate limits, or what happens to the issue's history. This is inadequate for a mutation tool with zero annotation coverage.

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 and appropriately sized for the tool's complexity, making it easy to parse 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 tool's complexity (a mutation operation with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain behavioral traits, usage context, or return values, leaving significant gaps for an agent to understand how 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?

Schema description coverage is 100%, so the schema already documents all parameters (issueKey, transitionId, comment). The description adds no additional meaning beyond what the schema provides, such as explaining what a 'transitionId' represents or how to obtain it, meeting the baseline for high schema coverage.

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 'Transition an issue to a new status' clearly states the verb ('transition') and resource ('issue'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'jira_update_issue', which might also change issue states, so it lacks sibling distinction for a perfect score.

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. It doesn't mention prerequisites (e.g., needing issue access), exclusions, or compare to siblings like 'jira_update_issue' for status changes, leaving usage unclear.

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

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