Skip to main content
Glama

Update Jira issue

update_issue
DestructiveIdempotent

Modify fields on a Jira issue such as summary, description, priority, assignee, and labels. Omit parameters to leave values unchanged; pass null to clear a field.

Instructions

Update fields on a Jira issue. Omitted parameters stay unchanged. Labels replace the current set. Pass other Jira fields through fields. Use a null value to clear a field, e.g. {"assignee": null}. Returns the updated field IDs. To change status, use transition_issue.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issue_key": "<issue_key>"
    },
    "name": "update_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOther fields in Jira REST format, keyed by field ID. A null value clears the field.
labelsNoLabels that replace the current ones. [] removes all.
summaryNoNew title, at most 255 characters.
priorityNoPriority name, e.g. High.
config_idNoJira instance to use, from list_configs. Omit for the default.
issue_keyYesIssue key, e.g. ONE-123.
descriptionNoPlain-text description. Blank lines separate paragraphs.
assignee_account_idNoAtlassian account ID of the assignee.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the specifics an agent needs: partial-update semantics, that labels are wholesale replaced (not merged), and that null is the clearing mechanism — exactly the destructive behavior the annotation only hints at. It also notes the return payload (updated field IDs).

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?

Five short sentences, front-loaded with the verb and resource; each sentence carries a distinct rule (partial update, labels replacement, fields passthrough, null clearing, status alternative). No filler.

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

Completeness4/5

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

Complete for a mutation tool: semantics of omission, replacement, and clearing are covered, and the return value is summarized despite no output schema. It omits permission requirements or error behavior (e.g. invalid issue_key or field ID), which would be the last gap to close.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds value beyond the schema by defining the null-clearing convention globally and giving a concrete example ({"assignee": null}) plus the rule that arbitrary Jira fields go through the `fields` bag. It stops short of explaining the anyOf/null pattern for every top-level parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Update fields on a Jira issue") and immediately distinguishes itself from the closest sibling by naming transition_issue for status changes. An agent can classify the tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes status changes to transition_issue and otherwise scopes the tool to field updates. It also gives the operative usage rules: omitted params stay unchanged, labels replace the whole set, and null clears a field.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.