Skip to main content
Glama

jira_update_issue

Update a Jira issue's fields including summary, markdown description, simple fields, and rich text fields with automatic Atlassian Document Format conversion.

Instructions

Updates fields on a Jira issue.

Args:
    issue_key: The issue key (e.g. "PROJ-123").
    summary: New summary text.
    description: New description in markdown. Supports headings, bold,
        italic, strikethrough, links, code blocks, lists, tables, etc.
    additional_fields: Dict of field_id -> value for simple fields
        (plain text, dates, numbers, selects).
        Use jira_list_fields to discover field IDs.
        Example: {"duedate": "2026-04-01", "labels": ["bug"]}
    rich_text_fields: Dict of field_id -> markdown string for rich text
        fields that need ADF conversion (e.g. Developer Notes,
        Deployment Info). These get converted to Atlassian Document
        Format automatically.
        Example: {"customfield_10402": "## Plan
  • Step 1

  • Step 2"}

    Mentioning users (in description and rich_text_fields): First call jira_search_users to find the accountId, then use @[accountId] in the text (e.g. @[712020:abc123]).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_keyYes
summaryNo
descriptionNo
additional_fieldsNo
rich_text_fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It explains that rich text fields undergo ADF conversion, and that markdown is supported for description and rich text. It does not disclose idempotency or error handling, but covers core behavior well.

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?

Well-structured with sections for each parameter type and usage tips. Some repetition (e.g., mentioning markdown twice) but every sentence adds value. Could be slightly more concise, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 5 parameters (1 required), no annotations, but an output schema exists. The description covers all parameters, provides examples, and explains conversion behavior. It is thorough and leaves no major gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, description fully explains each parameter: issue_key format, summary, description with markdown support, additional_fields with example, rich_text_fields with ADF conversion note. Provides concrete examples for additional_fields and rich_text_fields.

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 it updates fields on a Jira issue, a specific verb-resource pair. It distinguishes itself from sibling tools like jira_create_issue and jira_transition_issue by focusing on field updates.

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?

Provides guidance on when to use additional_fields vs rich_text_fields, and instructs to use jira_list_fields to discover field IDs. Mentions user mentioning prerequisite (jira_search_users). However, it does not explicitly exclude usage for transitions or other operations.

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/tingyiy/atlassian-mcp-server'

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