Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Update issue

jira_update_issue
Idempotent

Update selected fields of an existing Jira issue while leaving all other fields unchanged. Use it to change summary, description, labels, priority, due date, parent, components, or custom fields.

Instructions

Update fields of an issue. Only the provided fields change. Use jira_transition_issue to change status and jira_assign_issue to change assignee.

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

Input Schema

NameRequiredDescriptionDefault
issueYesIssue key ('ABC-123'), instance-prefixed key ('work:ABC-123') or full browse URL ('https://acme.atlassian.net/browse/ABC-123').
labelsNoReplaces all labels.
parentNo
dueDateNoYYYY-MM-DD, or empty string to clear.
summaryNo
instanceNoJira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists.
priorityNo
componentsNo
descriptionNoReplaces the description (light Markdown supported).
customFieldsNoExtra raw Jira fields, e.g. {"customfield_10016": 5}. Values are sent as-is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare the full safety profile (readOnly=false, destructive=false, idempotent=true, openWorld=true), so the bar is low. The description contributes one genuinely useful behavioral fact beyond them: 'Only the provided fields change', i.e. PATCH-style partial mutation semantics. It does not cover failure modes, permission requirements, or what a successful update returns.

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?

Three short sentences, front-loaded with the core action, followed by the mutation-semantics qualifier and the sibling routing. No filler and no repetition of schema content.

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 with a nested customFields object and no output schema, the description plus the rich schema covers what an agent needs to invoke it correctly, including instance resolution. The notable remaining gap is the absence of any statement about what a successful call returns or how failures surface, which matters somewhat given there is no output schema.

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 coverage is 60%, with strong inline descriptions on the highest-risk parameters (issue formats, instance routing, labels replacement, dueDate clearing, customFields pass-through). The description's 'only the provided fields change' reinforces partial-update semantics for omitted parameters, which the schema does not state, but it adds nothing about the undocumented fields (parent, summary, priority, components).

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?

The description states a specific verb and resource ('Update fields of an issue') and immediately distinguishes this tool from the two siblings that handle the most commonly confused adjacent operations (status and assignee). An agent can pick this tool over jira_transition_issue or jira_assign_issue without opening any schema.

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

Usage Guidelines4/5

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

It explicitly routes two out-of-scope operations to named alternatives, which is exactly the guidance an agent needs to avoid misfiring on status/assignee. It stops short of stating exclusions for other overlaps (deletion, copying, creating) or prerequisites such as required permissions, so it is clear context rather than a full when/when-not map.

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