Skip to main content
Glama

jira_update_comment

Update an existing Jira issue comment by replacing its full text using the issue key and comment ID. Retrieve the comment ID first from the issue or comments list.

Instructions

Edit/modify an existing comment on a Jira issue. You need the comment ID which can be obtained from jira_get_comments or jira_get_issue. Replaces the entire comment text.

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>",
      "commentId": "<commentId>",
      "body": "<body>"
    },
    "name": "jira_update_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesNew comment text (replaces existing text entirely)
issueKeyYesIssue key containing the comment (e.g., KP-123)
commentIdYesID of the comment to update (get from jira_get_comments)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the most important trait: the body replaces the existing text entirely rather than appending. However, it says nothing about permissions required, whether prior text is recoverable, or what happens on a stale/invalid comment ID.

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 the action front-loaded, then the ID prerequisite, then the replacement caveat. No filler and nothing redundant.

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?

For a simple three-parameter mutation with no output schema, the description covers action, prerequisite sourcing, and destructive replacement semantics. Only permission requirements and failure behavior are left unstated, which is a minor gap at this complexity.

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%, so all three parameters are already documented with examples and the replacement semantics. The description adds only the provenance hint for commentId, which is already noted in the schema; baseline 3 applies.

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?

States a specific verb and resource ('Edit/modify an existing comment on a Jira issue'), which cleanly separates it from the add/delete comment siblings. It does not name those siblings explicitly, so the differentiation is implied by the verb rather than spelled out.

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 a concrete prerequisite workflow: the comment ID must come from jira_get_comments or jira_get_issue, which tells the agent how to reach a callable state. It stops short of explicit when-not guidance or naming jira_add_comment as the alternative for new text.

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