Skip to main content
Glama
freema

mcp-jira-stdio

by freema
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

jira_update_issue

Update a Jira issue by key, modifying summary, description, priority, assignee, labels, components, or fix versions. Change only specified fields; description supports markdown, ADF, or plain text.

Instructions

Updates an existing Jira issue by its key. Supports updating summary, description, priority, assignee, labels, components, and fix versions. Description format is controlled by the "format" parameter (default: markdown). Only specified fields will be updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoDescription format: "markdown" (converts Markdown to ADF), "adf" (use as-is ADF object), "plain" (converts plain text to ADF with basic formatting). Default: "markdown"markdown
labelsNoNew labels (replaces existing)
parentNoNew parent issue key (e.g., PROJECT-100). Set to empty string to remove the parent.
summaryNoNew summary
assigneeNoNew assignee account ID
issueKeyYesIssue key to update
priorityNoNew priority
componentsNoNew components (replaces existing)
descriptionNoNew description. Accepts plain text or ADF object.
fixVersionsNoNew fix version names (replaces existing fix versions)
returnIssueNoWhen false, skip fetching full issue after update

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.12.0
    • addedInput schema / properties / fixVersions
      Added value: +{
+  "description": "New fix version names (replaces existing fix versions)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed2 schema fields changedv1.11.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / description / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {}
+]
  3. Changed14 schema fields changedv1.10.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / assignee / description
      Previous value: -"New assignee account ID (optional, use null string to unassign)"New value: +"New assignee account ID"
    • changedInput schema / properties / components / description
      Previous value: -"New components array (replaces existing components) - optional"New value: +"New components (replaces existing)"
    • changedInput schema / properties / description / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "object"
-  }
-]New value: +[
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / description / description
      Previous value: -"New issue description (optional). Accepts plain text (auto-formatted to ADF) or an ADF document."New value: +"New description. Accepts plain text or ADF object."
    • addedInput schema / properties / format
      Added value: +{
+  "default": "markdown",
+  "description": "Description format: \"markdown\" (converts Markdown to ADF), \"adf\" (use as-is ADF object), \"plain\" (converts plain text to ADF with basic formatting). Default: \"markdown\"",
+  "enum": [
+    "markdown",
+    "adf",
+    "plain"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / issueKey / description
      Previous value: -"Issue key to update (e.g., PROJECT-123)"New value: +"Issue key to update"
    • changedInput schema / properties / labels / description
      Previous value: -"New labels array (replaces existing labels) - optional"New value: +"New labels (replaces existing)"
    • addedInput schema / properties / parent
      Added value: +{
+  "description": "New parent issue key (e.g., PROJECT-100). Set to empty string to remove the parent.",
+  "type": "string"
+}
    • changedInput schema / properties / priority / description
      Previous value: -"New priority name (e.g., High, Medium, Low) - optional"New value: +"New priority"
    • removedInput schema / properties / returnIssue / default
      Removed value: -true
    • changedInput schema / properties / returnIssue / description
      Previous value: -"If false, returns a success message without fetching the updated issue"New value: +"When false, skip fetching full issue after update"
    • changedInput schema / properties / summary / description
      Previous value: -"New issue summary/title (optional)"New value: +"New summary"
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

The description goes beyond the single readOnlyHint=false annotation by disclosing that only specified fields change, so an agent knows omitted fields are not overwritten. It also calls out the description format behavior and its default. It does not mention that array fields replace existing values, but the schema already states 'replaces existing' for labels, components, and fixVersions.

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 with no filler: the target resource, supported fields, format control, and partial-update guarantee each earn their place. Key facts are front-loaded and easy to scan.

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?

The description plus 100% schema coverage gives an agent the information needed to select and invoke the tool correctly, including the partial-update behavior and format default. It omits `parent` from the narrative and does not describe return behavior, but the schema covers both `parent` and `returnIssue`, so no critical selection information is missing.

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 descriptions cover 100% of the 11 parameters, so the baseline of 3 applies. The prose repeats the field names and format default but adds no semantic detail beyond what the schema already provides.

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 opens with a specific verb and resource: 'Updates an existing Jira issue by its key,' and enumerates the editable fields. This clearly disambiguates it from sibling tools like jira_create_issue, jira_transition_issue, and jira_add_comment. The only minor omission is that it does not list `parent` among updatable fields, but the core purpose is unmistakable.

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

Usage Guidelines3/5

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

The phrase 'Only specified fields will be updated' conveys partial-update semantics, which is important usage guidance. However, the description does not explicitly say when to choose this tool over create/transition/comment siblings, nor does it state prerequisites beyond the issue key. Usage context is implied rather than explicit.

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