Skip to main content
Glama

jira_update_issue

Update specified fields on an existing Jira issue—such as summary, description, assignee, priority, labels, components, fix versions, due date, or custom fields—while leaving unspecified fields unchanged.

Instructions

Modify an existing Jira issue's fields (summary, description, assignee, priority, labels, components, fix versions, due date, custom fields). Only the fields you specify will be changed - others remain unchanged. Custom fields use field ids (customfield_10006) or a unique name from jira_get_edit_meta, with raw REST values. Do not call jira_get_fields before writing. To change status/workflow state, use jira_transition_issue instead. To add comments, use jira_add_comment.

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": {
      "issueKey": "<issueKey>"
    },
    "name": "jira_update_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelsNoNew labels (replaces existing)
dueDateNoNew due date in YYYY-MM-DD format
summaryNoNew issue title/summary
assigneeNoUsername to assign to (use empty string "" to unassign, use jira_get_assignable_users to find valid usernames)
issueKeyYesIssue key to update (e.g., KP-123)
priorityNoPriority name (e.g., Highest, High, Medium, Low, Lowest)
componentsNoNew components (replaces existing)
descriptionNoNew description text
fixVersionsNoNew fix versions (replaces existing)
customFieldsNoCustom fields keyed by field id (e.g. customfield_10006) or a unique name from that issue type's meta. Values are raw Jira REST payloads, not display names. Call jira_get_edit_meta for schema/allowedValues and unique names. Examples: number 5, string "text", select {"value":"Yes"}, Server user {"name":"username"}, multi-select [{"value":"A"}], null to clear. Do not call jira_get_fields before update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and largely meets it: it discloses partial-update semantics ('Only the fields you specify will be changed'), the need for raw REST payloads in custom fields, and the id/unique-name keying. It does not cover permission requirements, whether watchers are notified, or what happens on rejected values, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and field list, then routing rules, with no filler sentences. There is minor duplication between the description's custom-field guidance and the customFields schema text, which is the only thing holding it below a 5.

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?

For a 10-parameter mutation tool with a nested object and no annotations, the definition covers the risky parts: partial updates, raw payload shapes, keying strategy, and the correct prep tool. The notable gap is that no output schema exists and the description never states what an update returns, so an agent cannot anticipate the response shape.

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 every parameter thoroughly, including replacement semantics and custom field examples. The description's custom-field sentences largely restate what customFields already says, adding value mainly through the edit-meta pointer and the partial-update framing. Baseline 3 is appropriate.

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 ('Modify an existing Jira issue's fields') and enumerates the mutable field set, so scope is unambiguous. It also explicitly distinguishes itself from jira_transition_issue and jira_add_comment, which are the two most plausible confusions.

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?

Gives explicit routing rules: status/workflow goes to jira_transition_issue, comments go to jira_add_comment, and it names a negative rule ('Do not call jira_get_fields before writing') plus the correct prerequisite (jira_get_edit_meta). An agent has no ambiguity about when to pick this tool.

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