Skip to main content
Glama
Sign In
Jira Enterprise MCP

Jira Enterprise MCP

by w-10-m
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jira_list_issue_comments

Retrieve all comments for a Jira issue by providing its issue key. Returns a simplified list of comments.

Instructions

List comments for a Jira issue in a simplified shape.

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_list_issue_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueKeyYesJira issue key, for example ABC-123

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 of behavioral disclosure. It does not mention whether comments are paginated, ordered, require authentication, or what 'simplified shape' entails. This is insufficient for an agent to understand the tool's behavior.

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, well-structured sentence with no unnecessary words. It efficiently communicates the core action and resource, earning its place without fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list operation with one parameter and no output schema, the description is too minimal. It fails to explain the return format, pagination, or any limitations, leaving the agent without critical context for effective use.

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 coverage is 100% for the single parameter (issueKey) with a clear description. The tool description adds no additional meaning beyond the schema, which is acceptable given the baseline of 3 when coverage is high.

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 clearly states the action (list comments) and the resource (a Jira issue), using a specific verb+resource pair. It distinguishes from sibling tools like jira_add_comment and jira_get_issue. The phrase 'in a simplified shape' adds slight ambiguity but does not obscure the overall purpose.

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, nor are any exclusions or prerequisites mentioned. The description only states what it does, leaving the agent to infer usage context from the name alone.

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

Deploy Server

Other Tools