MCP Jira Server

jira_get_comments

Fetch all comments from a Jira issue by providing its issue key to review discussion history and track updates.

Instructions

Get all comments from 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>"
    },
    "name": "jira_get_comments"
  }
}

Input Schema

Name	Required	Description	Default
`issueKey`	Yes	The Jira issue key

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Sep 29, 2026

TDQS

B3.2/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 burden of behavioral disclosure. It confirms a read operation but does not mention return format, ordering, pagination, error conditions, or authentication requirements, leaving key behavioral expectations unstated.

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 short sentence with no filler or redundant information. It front-loads the core action and resource clearly, making it easy to parse quickly.

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?

This is a simple retrieval tool with one well-documented parameter and no output schema, so the description covers the essential information needed to invoke it. It could be slightly stronger if it mentioned that the result is a list of comment objects, but the core usage is sufficiently clear.

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 covers 100% of the parameter documentation, with 'issueKey' described as 'The Jira issue key'. The description adds no extra semantic detail beyond this baseline, so the schema handles the parameter documentation adequately.

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 uses a specific verb ('Get') and a specific resource ('all comments from a Jira issue'), making the tool's purpose clear. It does not explicitly distinguish itself from siblings like jira_get_issue, but the resource is unambiguous enough for an agent to identify the intended operation.

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 such as jira_add_comment or jira_get_issue. There is no mention of use cases, prerequisites, or exclusions, so the agent must rely on the tool name alone to decide.

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

Deploy Server