Skip to main content
Glama
freema

mcp-jira-stdio

by freema
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

jira_update_issue

Update a Jira issue by its key. Change summary, description, priority, assignee, labels, or components; only the fields you specify get updated, with markdown or plain text description support.

Instructions

Updates an existing Jira issue by its key. Supports updating summary, description, priority, assignee, labels, and components. 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.
returnIssueNoWhen false, skip fetching full issue after update

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+  },
+  {}
+]
  2. 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"
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=false, which matches the update behavior. The description adds that description format is controlled by a parameter and only specified fields are updated, but does not disclose potential side effects like triggers, permissions, or return value.

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?

Two sentences cover purpose, supported fields, and format details without redundancy. No unnecessary words.

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?

Given 10 parameters and no output schema, the description covers the core update operation well. It lacks mention of return value or failure behavior, but is otherwise complete for the task.

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 100% with detailed parameter descriptions. The description adds a high-level overview of supported fields, but does not provide significant new meaning beyond the schema. 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?

The description clearly states the tool updates an existing Jira issue by key and lists supported fields (summary, description, priority, assignee, labels, components), distinguishing it from sibling tools like jira_create_issue (create) and jira_transition_issue (status change).

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?

The description implies use when you need to modify specific fields of an existing issue, but it does not explicitly exclude alternatives like jira_transition_issue for status changes or jira_add_comment for comments. It states 'Only specified fields will be updated' which guides partial updates.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/freema/mcp-jira-stdio'

If you have feedback or need assistance with the MCP directory API, please join our Discord server