Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete Tracker worklog record

tracker_worklog_delete
Destructive

Permanently delete a worklog record from a Tracker issue using issue_key and record_id. Use worklog_list to obtain record_id; this action is irreversible.

Instructions

Permanently delete a worklog record from a Tracker issue (irreversible).

Get record_id from worklog_list. Returns an acknowledgement on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_keyYesIssue key, e.g. QUEUE-123.
record_idYesWorklog record id, from ``worklog_list``.

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",
-  "record_id"
-]New value: +[
+  "issue_key",
+  "record_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, readOnlyHint=false, and idempotentHint=false, so the safety profile is largely covered. The description adds meaningful context beyond that: the deletion is permanent/irreversible and the call returns an acknowledgement on success, which reduces uncertainty about what happens after invocation.

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, front-loaded with the destructive nature of the call and then the prerequisite. Every clause earns its place with no filler.

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 two-parameter delete with full schema coverage, complete annotations, and no output schema, the description covers purpose, irreversibility, prerequisite, and return behavior. It could add auth/permission requirements, but nothing critical is missing for correct invocation.

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% (both `issue_key` and `record_id` are documented in the schema), so the baseline is 3. The description only restates that `record_id` comes from `worklog_list`, adding a small amount of provenance info but no new format or constraint details.

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 (delete), resource (worklog record), and scope (from a Tracker issue), plus the irreversibility qualifier. It also names the sibling tool `worklog_list` as the source of the id, so an agent can tell it apart from read-side worklog tools.

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?

The description implies the workflow by telling the agent where to obtain `record_id` (`worklog_list`), which is useful prerequisite guidance. However, it gives no explicit when-to-use vs. when-not guidance (e.g., use `worklog_update` to amend instead of deleting) among the many sibling delete/update tools.

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