Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Tracker issue comments

tracker_comments_list
Read-onlyIdempotent

List comments for a Tracker issue by key, automatically paginating results and capping them unless a limit is set.

Instructions

All comments on a Tracker issue, auto-paginated via the relative id-cursor.

Capped at the configured item cap unless limit is given, so very long threads are truncated at the cap rather than fetched forever.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax comments to return; omitted means the configured cap (YCLI__HTTP__MAX_ITEMS).
expandNoExtra blocks to include in the reply.
issue_keyYesIssue key, e.g. QUEUE-123.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.122.1
    • addedInput schema / properties / issue_key
      Added value: +{
+  "description": "Issue key, e.g. QUEUE-123.",
+  "type": "string"
+}
    • removedInput schema / properties / key
      Removed value: -{
-  "description": "Issue key, e.g. QUEUE-123.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "key"
-]New value: +[
+  "issue_key"
+]
  2. First observedv0.67.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: auto-pagination via a relative id-cursor and silent truncation at the configured item cap unless limit is passed. That truncation warning is the kind of trait annotations cannot express.

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?

Two sentences, zero filler, and the leading clause names the resource before the pagination detail. Every sentence earns its place.

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 read-only list tool with full schema coverage and safety annotations, the description supplies the pagination and truncation context an agent needs. The absence of output-schema explanation is fine since no output schema exists and the id-cursor is named.

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%, so the baseline is 3. The description reinforces the limit semantics (cap vs explicit limit) but adds no syntax or format detail for expand or issue_key beyond what the schema already states.

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?

States a specific verb+resource: lists all comments on a Tracker issue. Clear enough to distinguish from write siblings like tracker_comments_create or tracker_comments_update. It does not explicitly differentiate from tracker_comments_get or tracker_entities_comments_list, 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 Guidelines2/5

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

No when-to-use guidance and no mention of alternatives. The description never says to use tracker_comments_get when a single comment id is known, nor does it clarify the relationship to tracker_entities_comments_list. Only the pagination/cap behavior is implied context.

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