Atlassian MCP Server

jira_update_issue

Update existing Jira issues by modifying their summary, description, or priority. Provide the issue key to identify the target issue.

Instructions

Обновить существующую задачу в Jira

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

Name	Required	Description
`summary`	No	Новый заголовок задачи
`issueKey`	Yes	Ключ задачи (например: 'PROJ-123')
`priority`	No	Новый приоритет (например: 'High', 'Medium', 'Low')
`description`	No	Новое описание задачи

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 7, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotation coverage is empty, so the description must carry the full burden. It only says 'update existing issue' and does not clarify whether updates are partial or full replacement, whether permissions are needed, or what side effects occur. This is too thin for a mutating tool.

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?

The description is one concise, front-loaded sentence that earns its place. It sacrifices useful behavioral detail, but as a concise statement of purpose it is well structured.

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?

Despite full parameter schema coverage, this is a mutation tool with no annotations and no output schema. The description does not clarify update semantics (partial vs full) or prerequisites, leaving an agent uncertain about important call behavior.

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% with each parameter documented, so the baseline is 3. The tool description adds no extra parameter semantics, but none are needed beyond the schema.

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 action (update) and resource (existing Jira issue), and the word 'existing' distinguishes it from creation tools like jira_create_issue and from read tools like jira_get_issue.

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 phrase 'existing issue' provides clear context that this tool is for modifying an already-created issue, distinguishing it from create/get siblings. However, it does not explicitly name alternatives or when-not conditions, so it stops short of a 5.

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

Deploy Server