Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Execute Tracker issue transition

tracker_transitions_execute

Move a Tracker issue to a new status by executing a workflow transition. Pass issue key, transition ID, and fields like resolution or comment.

Instructions

Move a Tracker issue through a workflow transition (change its status).

Get transition_id from transitions_list. body may be empty or carry issue fields to set on transition, e.g. a resolution when closing. Returns the transitions available from the new status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesTyped request body for ``POST /issues/{key}/transitions/{id}/_execute``. Open-ended: any issue field can be set on transition (e.g. a resolution when closing), so ``extra="allow"`` lets arbitrary fields pass through unvalidated while the common fields below still document themselves in the MCP schema.
issue_keyYesIssue key, e.g. QUEUE-123.
transition_idYesTransition id, from ``transitions_list``.

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 ``POST /issues/{key}/transitions/{id}/_execute``.\n\nOpen-ended: any issue field can be set on transition (e.g. a resolution when closing), so\n``extra=\"allow\"`` lets arbitrary field key=value pairs (from the CLI's ``-F``) pass through\nunvalidated while the common fields below still document themselves in the MCP schema."New value: +"Typed request body for ``POST /issues/{key}/transitions/{id}/_execute``.\n\nOpen-ended: any issue field can be set on transition (e.g. a resolution when closing), so\n``extra=\"allow\"`` lets arbitrary fields pass through\nunvalidated while the common fields below still document themselves in the MCP schema."
    • 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",
-  "transition_id",
-  "body"
-]New value: +[
+  "issue_key",
+  "transition_id",
+  "body"
+]
  2. First observedv0.67.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the mutation semantics are covered structurally. The description adds value by explaining that body may be empty and that the call returns the transitions available from the new status, which the annotations do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core action and then the prerequisite and body semantics. No filler, though the parenthesis restating 'change its status' is mildly redundant.

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?

There is no output schema, and the description compensates by stating the call returns the transitions available from the new status. Combined with the schema's full parameter coverage and the annotations' safety profile, an agent has nearly everything needed to invoke it correctly.

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 the nested body is fully documented, so the schema does the heavy lifting. The description adds only that body may be empty or carry issue fields such as a resolution, which is marginal beyond what the schema already states.

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 (Move) and resource (Tracker issue through a workflow transition) plus a clarifying synonym (change its status). It is easy to separate from siblings like transitions_list (which lists rather than executes).

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?

Explicitly routes the agent to ``transitions_list`` to obtain ``transition_id``, which is a real prerequisite. It doesn't state when NOT to use this (e.g. vs. tracker_issues_transition_bulk), so it falls short of a full when/when-not/alternatives treatment.

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