JIRA MCP Server

jira_add_comment

Add a comment to a JIRA issue using its issue key and comment text. Keep stakeholders informed by posting updates directly to the relevant issue.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.13Jul 31, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, and the description only states the action without disclosing side effects, permission requirements, or return behavior. As a write operation, it would benefit from noting whether it requires edit permissions or returns the created comment.

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, clear sentence that front-loads the action and resource with no wasted words.

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 with two fully documented parameters, but the description lacks any mention of return values or success indicators, and no output schema exists to fill that gap. It is adequate for a basic understanding but not complete.

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 fully describes both parameters (issueKey and body) with examples, so the description adds no additional parameter-level information. Baseline of 3 applies due to 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 clearly states the action (add) and the resource (a comment to a JIRA issue), distinguishing it from sibling tools like jira_get_issue_comments or jira_update_issue.

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 over alternatives, such as jira_get_issue_comments for reading comments or jira_update_issue for editing fields. The description simply states the action without any context or exclusions.

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