Skip to main content
Glama

jira_update_issue

Modify existing Jira issues by updating fields like summary, description, priority, assignee, or labels to reflect current status and requirements.

Instructions

Update an existing Jira issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe Jira issue key
summaryNoNew summary
descriptionNoNew description
priorityNoNew priority name
assigneeNoNew assignee username
labelsNoNew labels

Implementation Reference

  • src/index.ts:275-294 (registration)
    Tool registration in the list of available tools, including name, description, and input schema.
    {
      name: "jira_update_issue",
      description: "Update an existing Jira issue",
      inputSchema: {
        type: "object",
        properties: {
          issueKey: { type: "string", description: "The Jira issue key" },
          summary: { type: "string", description: "New summary" },
          description: { type: "string", description: "New description" },
          priority: { type: "string", description: "New priority name" },
          assignee: { type: "string", description: "New assignee username" },
          labels: {
            type: "array",
            items: { type: "string" },
            description: "New labels",
          },
        },
        required: ["issueKey"],
      },
    },
  • Zod schema for validating input parameters to the jira_update_issue tool.
    const UpdateIssueSchema = z.object({
      issueKey: z.string().describe("The Jira issue key"),
      summary: z.string().optional().describe("New summary"),
      description: z.string().optional().describe("New description"),
      priority: z.string().optional().describe("New priority name"),
      assignee: z.string().optional().describe("New assignee username"),
      labels: z.array(z.string()).optional().describe("New labels"),
    });
  • MCP tool handler for jira_update_issue: parses arguments, constructs update fields, calls jiraClient.updateIssue, and returns success message.
    case "jira_update_issue": {
      const { issueKey, summary, description, priority, assignee, labels } =
        UpdateIssueSchema.parse(args);
      await jiraClient.updateIssue(issueKey, {
        fields: {
          ...(summary && { summary }),
          ...(description && { description }),
          ...(priority && { priority: { name: priority } }),
          ...(assignee && { assignee: { name: assignee } }),
          ...(labels && { labels }),
        },
      });
      return {
        content: [
          { type: "text", text: `Issue ${issueKey} updated successfully` },
        ],
      };
    }
  • Core implementation of issue update: sends PUT request to Jira REST API /issue/{issueKey} with update data.
    async updateIssue(
      issueKey: string,
      data: JiraUpdateIssueRequest
    ): Promise<void> {
      await this.request<void>(`/issue/${issueKey}`, {
        method: "PUT",
        body: JSON.stringify(data),
      });
    }
  • TypeScript interface defining the structure of the update request sent to Jira API.
    export interface JiraUpdateIssueRequest {
      fields: {
        summary?: string;
        description?: string;
        priority?: { name: string };
        assignee?: { name: string };
        labels?: string[];
        [key: string]: unknown;
      };
    }
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. While 'Update' implies a mutation, the description doesn't mention permission requirements, whether partial updates are allowed, what happens to unspecified fields, or what the response looks like. For a mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 gets straight to the point with zero wasted words. It's appropriately sized for a tool with good schema documentation and is perfectly front-loaded with the essential 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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address behavioral aspects like permissions, partial updates, or response format, nor does it differentiate from similar sibling tools. The combination of mutation operation + zero annotation coverage + multiple similar siblings requires more comprehensive guidance than provided.

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 description adds no parameter information beyond what's already in the schema, which has 100% coverage with clear descriptions for all 6 parameters. The baseline score of 3 reflects that the schema adequately documents parameters, though the description could have added context about how parameters interact or which are most commonly used.

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 'Update an existing Jira issue' clearly states the action (update) and resource (Jira issue), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'jira_update_issue_advanced' or 'jira_assign_issue', which also modify issues in different ways.

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. With siblings like 'jira_update_issue_advanced', 'jira_assign_issue', and 'jira_transition_issue' that also modify issues, there's no indication of what distinguishes this basic update from those more specialized operations.

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/yogeshhrathod/JiraMCP'

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