Skip to main content
Glama
kornbed

Jira MCP Server for Cursor

update_status

Change the status of a Jira ticket by specifying the ticket ID and transition ID to move it through workflow stages.

Instructions

Update the status of a Jira ticket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticketIdYesThe Jira ticket ID
statusYes

Implementation Reference

  • The handler function that performs the Jira status update by calling the doTransition API with the provided ticket ID and transition ID. Includes config validation and error handling.
    async ({ ticketId, status }: { ticketId: string; status: StatusUpdate }) => {
      const configError = validateJiraConfig();
      if (configError) {
        return {
          content: [{ type: "text", text: `Configuration error: ${configError}` }],
        };
      }
    
      try {
        await jira.issues.doTransition({
          issueIdOrKey: ticketId,
          transition: { id: status.transitionId },
        });
    
        return {
          content: [{ type: "text", text: `Updated status of ${ticketId}` }],
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Failed to update status: ${(error as Error).message}` }],
        };
      }
    }
  • Zod schema for validating the 'status' input parameter of the update_status tool.
    const StatusUpdateSchema = z.object({
      transitionId: z.string().describe("The ID of the transition to perform"),
    });
  • TypeScript interface defining the shape of the status update input.
    interface StatusUpdate {
      transitionId: string;
    }
  • src/server.ts:345-375 (registration)
    Registration of the 'update_status' tool on the MCP server, specifying name, description, input schema, and handler function.
    server.tool(
      "update_status",
      "Update the status of a Jira ticket",
      {
        ticketId: z.string().describe("The Jira ticket ID"),
        status: StatusUpdateSchema,
      },
      async ({ ticketId, status }: { ticketId: string; status: StatusUpdate }) => {
        const configError = validateJiraConfig();
        if (configError) {
          return {
            content: [{ type: "text", text: `Configuration error: ${configError}` }],
          };
        }
    
        try {
          await jira.issues.doTransition({
            issueIdOrKey: ticketId,
            transition: { id: status.transitionId },
          });
    
          return {
            content: [{ type: "text", text: `Updated status of ${ticketId}` }],
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Failed to update status: ${(error as Error).message}` }],
          };
        }
      }
    );
  • Helper function used by the handler to validate Jira configuration environment variables.
    // Helper function to validate Jira configuration
    function validateJiraConfig(): string | null {
      if (!process.env.JIRA_HOST) return "JIRA_HOST environment variable is not set";
      if (!process.env.JIRA_EMAIL) return "JIRA_EMAIL environment variable is not set";
      if (!process.env.JIRA_API_TOKEN) return "JIRA_API_TOKEN environment variable is not set";
      return null;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Update' which implies a mutation, but doesn't disclose behavioral traits like required permissions, whether the change is reversible, rate limits, or what happens on success/failure. This leaves significant gaps for a mutation tool.

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, front-loaded sentence with zero waste—it directly states the tool's purpose without unnecessary words. This is appropriately sized for a simple update operation.

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 (mutation tool with nested parameters, no output schema, and no annotations), the description is incomplete. It lacks details on behavior, parameter usage, error handling, and output expectations, making it inadequate for safe and effective use by 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 50% (only 'ticketId' is described in schema, 'status' object lacks description). The description adds no parameter semantics beyond what's implied by the tool name—it doesn't explain what 'status' entails (e.g., transition IDs, valid values) or provide context for the nested object. Baseline 3 applies as schema does partial work.

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 ('Update') and resource ('status of a Jira ticket'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_ticket' or 'add_comment' beyond the obvious focus on status updates, so it's not fully specific to sibling context.

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 a valid ticket ID), exclusions, or how it relates to siblings like 'get_ticket' for checking current status or 'create_ticket' for initial setup.

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

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