Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Get comments

jira_get_comments
Read-only

Reads recent comments from a Jira issue as plain text, using an issue key, instance-prefixed key, or browse URL to provide discussion context.

Instructions

Read the most recent comments of an issue as plain text.

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": {
      "issue": "<issue>"
    },
    "name": "jira_get_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueYesIssue key ('ABC-123'), instance-prefixed key ('work:ABC-123') or full browse URL ('https://acme.atlassian.net/browse/ABC-123').
instanceNoJira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists.
maxResultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context by saying results are plain text and limited to the most recent comments (i.e., not the full comment history), but it does not say how many are returned, what the default ordering is, or what happens on issues with no comments.

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?

One short, front-loaded sentence with no wasted words. It is efficient but borders on under-specified rather than merely concise.

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?

For a three-parameter read tool with no output schema, the description should convey the shape of returned comments and the meaning of the undocumented maxResults. It covers the essentials (read, comments, plain text, recent) but leaves the return granularity and the result-limit behavior to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, below the threshold where the schema carries the load; notably maxResults has no description at all (only min/max bounds). The description's "most recent" implies recency ordering relevant to maxResults but never explains the parameter, the default count, or the 100 cap.

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?

Specific verb ("Read") plus resource ("comments of an issue") plus a format qualifier ("as plain text") and scope ("most recent"). It implicitly distinguishes itself from the write-side sibling jira_add_comment by saying "Read", but never names an alternative or clarifies how it differs from jira_get_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 when-to-use guidance, no exclusions, and no mention of when an agent should prefer this over jira_get_issue or jira_search. The only implicit cue is "most recent comments", which hints at a listing/recency use case but does not route the agent.

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