Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Tracker issue changelog

tracker_changelog_list
Read-onlyIdempotent

Fetch a Tracker issue's full edit history to track field, status, or workflow changes, with filtering, sorting, and limit options.

Instructions

Full changelog (edit history) for a Tracker issue.

Auto-paginated via the relative id-cursor. Capped at the configured item cap unless limit is given.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOrder of the changes.
fieldNoKeep the changes of this field, e.g. ``status``.
limitNoMax changes to return; omitted means the configured cap (YCLI__HTTP__MAX_ITEMS).
issue_keyYesIssue key, e.g. QUEUE-123.
change_typeNoKeep the changes of this type, e.g. ``IssueWorkflow``.

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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it is auto-paginated via a relative id-cursor and is capped at the configured item cap unless limit is passed.

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 tightly written sentences, front-loaded with the core purpose and immediately followed by the pagination/cap behavior. No filler or restatement of the tool name.

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 filtered list tool with full schema coverage and a clear annotation safety profile, the description covers purpose and pagination behavior well. With no output schema, it could say a bit more about the shape of returned change entries, but this is a minor gap.

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 schema already documents all five parameters including sort, field, change_type and limit. The description's only parameter-relevant statement (the cap vs. limit interaction) largely restates what the limit schema description already says, so it adds little beyond baseline.

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 states a specific verb and resource: returning the "Full changelog (edit history) for a Tracker issue." It is unambiguous, though it does not explicitly distinguish this from related history/event siblings such as tracker_entities_events_list.

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?

Usage is implied by the name and the issue-key requirement, but there is no explicit when-to-use guidance and no mention of alternatives (e.g. tracker_entities_events_list) or exclusions. Adequate but leaves routing to inference.

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