Skip to main content
Glama

jira_get_comments

Retrieve all comments from a Jira issue to review discussion history, feedback, and team notes, including comment text, authors, and timestamps.

Instructions

Retrieve all comments on a Jira issue. Returns comment text, author, and timestamps. Use this to see discussion history, feedback, or notes left by team members on an 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

NameRequiredDescriptionDefault
startAtNoStarting index for pagination
issueKeyYesIssue key to get comments for (e.g., KP-123)
maxResultsNoMaximum number of comments to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.5/5.0
Behavior3/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. It discloses the return fields, which is real behavioral information, but does not state comment ordering, whether pagination totals are returned, whether restricted/private comments are filtered, or permission requirements. Adequate for a zero-annotation tool but with clear gaps.

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

Conciseness4/5

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

Three short sentences, front-loaded with the verb and resource, followed by return shape and then purpose. No filler, though the closing 'use this to see...' sentence is somewhat redundant with the first.

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 read tool with 3 fully documented params and no output schema, the description covers purpose, return fields, and a use case. It could say more about ordering/pagination behavior given pagination parameters exist, but nothing critical blocks a correct invocation.

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% — issueKey, startAt, and maxResults are documented with an example and bounds. The description adds no semantics beyond the schema (no format hints, no note that pagination is offset-based or that maxResults caps at 100). Baseline 3 applies since the schema does the heavy lifting.

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 names a specific verb ('Retrieve') and resource ('comments on a Jira issue') and states the returned fields (comment text, author, timestamps). It does not explicitly differentiate itself from sibling read tools such as jira_get_changelog or jira_get_worklogs, so it falls short of a 5.

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?

It gives usage context ('see discussion history, feedback, or notes left by team members'), which implies when the tool is useful. However, there are no exclusions or named alternatives — an agent gets no guidance on whether worklog entries or status transitions belong elsewhere, and prerequisites such as permissions are unstated.

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