Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete Tracker checklist item

tracker_checklists_delete
Destructive

Permanently remove a single item from a Tracker issue checklist. Use the issue key and item ID from checklists_list; deletion is irreversible and returns remaining checklist.

Instructions

Permanently remove one item from a Tracker issue's checklist (irreversible).

Get item_id from checklists_list. Returns the issue with its remaining checklist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesChecklist item id, from ``checklists_list``.
issue_keyYesIssue key, e.g. QUEUE-123.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety bar is partly covered. The description adds value anyway by stressing permanence/irreversibility and disclosing the return shape ('the issue with its remaining checklist'), which the annotations do not.

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 short sentences, irreversibility and definition front-loaded, sourcing note second, zero filler. Nothing could be cut without losing information.

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?

With no output schema, the description helpfully states what comes back, and it covers the destructive/irreversible nature. It omits any note about required permissions or what happens when item_id is invalid, so it is slightly short of fully complete.

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% and both parameters are documented there, including item_id's source (checklists_list). The description restates that sourcing but adds no format, constraint, or edge-case detail beyond the schema.

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?

States a specific verb ('remove'), resource ('one item from a Tracker issue's checklist'), and scope ('one item'), which distinguishes it from the sibling tracker_checklists_clear that wipes the whole checklist. An agent can route correctly without opening the schema.

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?

Provides the prerequisite for the required item_id ('Get item_id from checklists_list'), which is genuine usage guidance. However, it never states when this is preferable to tracker_checklists_clear or the tracker_entities_checklists_items_delete variant, so alternative-selection is left 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