Skip to main content
Glama
vish288

mcp-atlassian-extended

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Jira Update Issue

jira_update_issue
Idempotent

Update Jira issue standard and custom fields by specifying the issue key plus field values. Use it to edit summaries, descriptions, labels, or customfield IDs in one call.

Instructions

Update a Jira issue's standard and custom fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoStandard fields to update (summary, description, labels, etc.)
issue_keyYesJira issue key (e.g. PROJ-123)
custom_fieldsNoCustom fields dict — keys are customfield_NNNNN IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.15.1
    • removedInput schema / properties / issue_key / minLength
      Removed value: -1
    • addedInput schema / properties / issue_key / pattern
      Added value: +"^[A-Za-z][A-Za-z0-9_]+-\\d+$"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.6.13

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and openWorldHint=true. The description adds no behavioral context beyond what annotations provide, such as whether unspecified fields are preserved, permission requirements, or side effects.

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?

A single, front-loaded sentence with no wasted words. It is efficient, though it provides no elaboration that might aid invocation.

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 output schema and only basic annotations, the description is too sparse. It does not explain whether the update merges or replaces fields, what happens to unmentioned fields, or any required permissions, leaving significant gaps.

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 all parameters including the distinction between standard and custom fields. The description's mention of 'standard and custom fields' adds no new semantic detail beyond the schema.

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?

States a specific verb ('Update') and resource ('Jira issue'), and adds that both standard and custom fields can be updated. It does not explicitly distinguish from sibling tools like jira_create_issue, but the resource is clear enough to identify the tool.

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?

No guidance on when to use this tool versus alternatives such as jira_create_issue or other update tools. There are no prerequisites, no exclusions, and no context about typical scenarios.

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

Deploy Server

Other Tools