jira-mcp-server

add_comment

Add a comment to a Jira issue by specifying the issue key and comment text, allowing you to update the issue directly.

Instructions

Add a comment to a Jira issue

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>",
      "comment": "<comment>"
    },
    "name": "add_comment"
  }
}

Input Schema

Name	Required	Description	Default
`comment`	Yes	The comment text
`issueKey`	Yes	Issue key (e.g., PROJ-123)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It does not mention side effects (e.g., appends a new comment), permissions needed, return values, or Jira markup support, leaving significant behavioral aspects unaddressed.

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 sentence, 'Add a comment to a Jira issue,' with no wasted words. It is front-loaded and clearly states the primary action.

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?

The tool is simple and the schema fully documents parameters, but the description omits usage context (when to choose this over alternatives) and return behavior. It is adequate but leaves gaps for the agent.

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?

The input schema has 100% description coverage for both parameters (issueKey and comment), so the description adds no additional semantic value. This aligns with the baseline for high schema coverage.

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 uses the specific verb 'add' with the resource 'comment' and target 'Jira issue', making the tool's function immediately clear. It distinguishes from sibling comment tools like update_comment and delete_comment through the word 'add'.

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?

No guidance is provided on when to use this tool versus updating or deleting comments, nor any prerequisites such as required permissions or Jira project context. The agent is left to infer usage from the verb alone.

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