Skip to main content
Glama

jira_update_issue

Modify existing Jira issues by updating fields like summary, description, priority, or assignee using the issue key.

Instructions

Update an existing Jira issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_keyYesIssue key (e.g., PROJ-123)
fieldsYesFields to update

Implementation Reference

  • The _update_issue method that executes the core logic for the jira_update_issue tool. It processes the input arguments, constructs the update fields dictionary, calls the Jira client's update_issue_field method, and returns a success message.
    async def _update_issue(self, arguments: dict) -> List[TextContent]:
        """Update an existing issue"""
        issue_key = arguments["issue_key"]
        fields = arguments["fields"]
        
        update_fields = {}
        if "summary" in fields:
            update_fields["summary"] = fields["summary"]
        if "description" in fields:
            update_fields["description"] = fields["description"]
        if "priority" in fields:
            update_fields["priority"] = {"name": fields["priority"]}
        if "assignee" in fields:
            update_fields["assignee"] = {"name": fields["assignee"]}
        
        self.jira_client.update_issue_field(issue_key, update_fields)
        
        return [TextContent(
            type="text",
            text=f"Updated issue: {issue_key}"
        )]
  • The inputSchema defining the expected parameters for the jira_update_issue tool: an object with required 'issue_key' (string) and 'fields' (object with optional summary, description, priority, assignee).
    inputSchema={
        "type": "object",
        "properties": {
            "issue_key": {
                "type": "string",
                "description": "Issue key (e.g., PROJ-123)"
            },
            "fields": {
                "type": "object",
                "description": "Fields to update",
                "properties": {
                    "summary": {"type": "string"},
                    "description": {"type": "string"},
                    "priority": {"type": "string"},
                    "assignee": {"type": "string"}
                }
            }
        },
        "required": ["issue_key", "fields"]
    }
  • The Tool object registration for jira_update_issue in the list_tools() function, which defines the tool's name, description, and input schema.
    Tool(
        name="jira_update_issue",
        description="Update an existing Jira issue",
        inputSchema={
            "type": "object",
            "properties": {
                "issue_key": {
                    "type": "string",
                    "description": "Issue key (e.g., PROJ-123)"
                },
                "fields": {
                    "type": "object",
                    "description": "Fields to update",
                    "properties": {
                        "summary": {"type": "string"},
                        "description": {"type": "string"},
                        "priority": {"type": "string"},
                        "assignee": {"type": "string"}
                    }
                }
            },
            "required": ["issue_key", "fields"]
        }
    ),
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's an update operation. It doesn't disclose behavioral traits like required permissions, whether updates are reversible, rate limits, error conditions, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this leaves critical gaps.

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?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized and front-loaded with the core purpose. Every word earns its place.

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?

Given this is a mutation tool with no annotations, no output schema, and complex nested parameters, the description is inadequate. It should explain what the tool returns, error handling, permissions needed, and how it differs from sibling tools. The current description leaves too many contextual 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 both parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema (e.g., format examples, field constraints, or update behavior). Baseline 3 is appropriate when schema does the heavy lifting.

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?

The description clearly states the verb ('Update') and resource ('an existing Jira issue'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'jira_transition_issue' which also modifies issues, missing an opportunity for clearer distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing issue_key), comparison with 'jira_transition_issue' for workflow changes, or when to use 'jira_create_issue' instead. The agent receives no usage context.

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/katsuhirohonda/jira-confluence-mcp'

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