Skip to main content
Glama

jira_add_comment

Add a comment to a Jira issue to share updates, ask questions, or communicate with team members using Jira wiki markup for formatting.

Instructions

Add a new comment to a Jira issue. Use this to leave notes, ask questions, provide updates, or communicate with team members about the issue. Supports Jira text formatting (wiki markup): bold, italic, {code}...{code} for code blocks, [link text|url] for links.

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

Input Schema

NameRequiredDescriptionDefault
bodyYesComment text. Supports Jira wiki markup: *bold*, _italic_, {code}code{code}, [link|url]
issueKeyYesIssue key to comment on (e.g., KP-123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses formatting support but says nothing about whether commenters need issue-level permission, whether watchers/assignees are notified, whether the call is idempotent on retry, or what the response contains. For a write operation with zero annotation coverage this is a meaningful gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the middle sentence ('leave notes, ask questions, provide updates') is filler that adds no decision-relevant information. The markup examples duplicate the schema's body description almost verbatim, so the definition carries redundancy.

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

Completeness3/5

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

This is a simple two-parameter mutation with no output schema and no annotations, and the description covers what it does and how to format text. It leaves out return behavior (e.g., the created comment id) and side effects like notifications, which an agent would want before calling a write tool.

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 both parameters are already documented, including the markup syntax on 'body' and the 'KP-123' example on 'issueKey'. The description's formatting sentence largely restates the schema's body description rather than adding new meaning, so the 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: 'Add a new comment to a Jira issue.' The verb 'add' plus 'new' implicitly separates it from jira_update_comment and jira_delete_comment. It stops short of explicitly naming those siblings, so it is clear but not maximally differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The sentence 'Use this to leave notes, ask questions, provide updates, or communicate with team members' gives use-case context, but it is generic motivation rather than routing guidance. There is no explicit when-not (e.g., use jira_update_comment to edit an existing comment, jira_add_worklog for time tracking) and no prerequisites such as required permissions.

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