Skip to main content
Glama
proprock

jira-mini-mcp

by proprock
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_comments

Read-onlyIdempotent

Fetch Jira issue comments with options for sort order, pagination, and a timestamp filter to focus on recent activity.

Instructions

List an issue's comments. order='desc' (default) returns newest first; 'asc' returns oldest first. start_at/limit paginate the logical, filtered, sorted collection (ties broken by comment id); limit=0 returns every remaining comment from start_at with no 100-comment cap. since (ISO-8601 with an explicit offset) keeps only comments created at or after that instant, and total reflects the filtered collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
orderNodesc
sinceNo
start_atNo
issue_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "get_commentsDictOutput",
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses important non-obvious behavior: pagination is on the logical filtered collection, ties are broken by comment id, limit=0 removes the 100-comment cap, and total reflects the filtered collection. This is rich, useful behavioral context.

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 front-loaded with the purpose and then packs dense, relevant details into a few sentences. There is no fluff or repetition; every segment adds meaningful operational information.

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

Completeness5/5

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

Given five parameters, zero schema descriptions, and no output schema, the description provides enough detail for an agent to invoke the tool correctly. It explains ordering, pagination, filtering, and a result-level concept (total) that would otherwise be unknown.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the full parameter documentation burden. It does: order values, start_at/limit pagination semantics, limit=0's special behavior, since's ISO-8601 offset requirement, and total semantics are all explained. issue_key is obvious from the purpose statement.

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 begins with a clear, specific verb and resource: 'List an issue's comments.' This distinguishes it from sibling tools like add_comment, get_issue, and get_changelog, whose names/purposes are different. The resource and action are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear operational guidance: it explains how ordering, pagination, and the since filter behave, including the special limit=0 behavior. It does not explicitly name alternatives or say when not to use this tool, but the context is sufficient and not misleading.

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