Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Update Tracker issue

tracker_issues_update
Idempotent

Update fields of a Tracker issue by changing only the keys present in the request body; returns the updated issue. Use transitions_execute for status changes.

Instructions

Update fields of a Tracker issue; only the keys present in body are changed.

Status is NOT changed here — use transitions_execute. Returns the updated issue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesTyped request body for ``PATCH /issues/{key}`` (update an issue; only sent fields change). ``extra="allow"`` lets any custom field pass through unvalidated. Status is NOT changed here — use ``transitions_execute``.
issue_keyYesIssue key, e.g. QUEUE-123.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.122.1
    • changedInput schema / properties / body / description
      Previous value: -"Typed request body for ``PATCH /issues/{key}`` (update an issue; only sent fields change).\n\n``extra=\"allow\"`` lets any custom field key=value pair pass through, matching the CLI's\n``-F key=value`` escape hatch. Status is NOT changed here — use ``transitions_execute``."New value: +"Typed request body for ``PATCH /issues/{key}`` (update an issue; only sent fields change).\n\n``extra=\"allow\"`` lets any custom field pass through unvalidated. Status is NOT changed\nhere — use ``transitions_execute``."
    • 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",
-  "body"
-]New value: +[
+  "issue_key",
+  "body"
+]
  2. First observedv0.67.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real behavioral value beyond that: partial-update semantics (only sent fields change), the status exclusion, and the fact that the updated issue is returned.

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?

Three short sentences, no filler. The core behavior is front-loaded, the routing hint comes second, and the return note closes it out.

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?

Covers what an agent needs for a no-output-schema mutation tool: mutation scope, the sibling to use for status, and the returned value. It could note the custom-field pass-through (extra='allow') that the schema mentions, but nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so per-field meanings (tags operators, type/priority key objects, YFM markdown description) are all handled by the schema, setting the baseline at 3. The description adds the partial-update contract for the body parameter — only supplied keys mutate — which is a genuine semantic beyond the schema's field list.

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 (update) and resource (Tracker issue) plus the precise scope: only keys present in body are changed. It explicitly separates itself from transitions_execute for status changes and, in a namespace crowded with update_bulk/move variants, makes clear this is the single-issue field updater.

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?

Gives an explicit when-not: status is not changed here, use transitions_execute. That routes the most likely confusion correctly, but there is no positive guidance on when to prefer this over tracker_issues_update_bulk or tracker_entities_update for the same operation.

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