Skip to main content
Glama
Sign In
ya-tracker-mcp

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

bulk_transition

Execute a workflow transition for multiple issues in one operation. Specify the transition ID and issue keys, with optional field updates and notifications.

Instructions

Bulk transition issues to a new status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "transition": "<transition>",
      "issues": "<issues>"
    },
    "name": "bulk_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
issuesYesList of issue keys
notifyNoSend notifications
valuesNoOptional field updates during transition
transitionYesTransition ID to execute

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits itself. It says only 'Bulk transition issues to a new status' and gives no information about partial failures, permission requirements, validation, or whether the operation is atomic. For a mutation tool, this is a significant transparency gap.

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?

The description is a single, clear sentence with no redundant words, making it highly concise and well-structured. It is slightly under-specified, but this is a conciseness dimension, not a completeness dimension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (bulk operation with optional notifications and field updates) and lack of annotations, the description is insufficient. It does not mention how 'bulk' affects behavior, what happens if some issues fail, or how this differs from single transition tools. An output schema exists, but that does not compensate for missing usage and behavioral context.

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%—all four parameters (issues, notify, values, transition) have descriptions in the input schema. The tool description adds no additional semantic meaning beyond the schema, so a baseline 3 is appropriate.

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?

The description uses the specific verb 'transition' with the resource 'issues' and the scope 'bulk', clearly distinguishing it from sibling tool transition_issue which handles single issues. It unambiguously states what the tool does.

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?

The word 'Bulk' provides clear contextual guidance that this tool is for transitioning multiple issues at once. However, it does not explicitly name alternatives or exclude single-issue transitions, stopping short of a 5.

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