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

ya-tracker-mcp

by imdeniil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_bulk_failed_issues

Retrieve a list of issues that failed in a Yandex Tracker bulk operation using the bulk change ID. Identify failures to address errors.

Instructions

Get list of issues that failed in a bulk operation.

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": {
      "bulk_change_id": "<bulk_change_id>"
    },
    "name": "get_bulk_failed_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_formatNoResponse format: "text" (default, markdown) or "json"text
bulk_change_idYesBulk operation ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavior disclosure. It states a read operation ('Get') but does not specify permissions, whether the operation has side effects, error conditions, or the format of the response. The addition of output_format in schema suggests customizable output, but the description does not acknowledge this.

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?

The description is a single concise sentence that immediately states the tool's purpose. There is no redundant information or fluff.

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

Completeness3/5

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

While the output schema likely covers return values, the description lacks contextual guidance about when to invoke this tool, such as after a bulk_update/bulk_move/bulk_transition. It also does not mention the output_format parameter, though the schema covers it. The one-liner is adequate but leaves the agent to infer the operational 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?

The input schema already fully documents both parameters: bulk_change_id is described as 'Bulk operation ID' and output_format explains its text/json options. The description adds no additional meaning beyond the schema, so it relies on the schema's coverage.

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 'Get' and clearly identifies the resource as 'issues that failed in a bulk operation.' This distinguishes it from sibling tools like get_bulk_status and bulk_update, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of pairing with bulk operations or that get_bulk_status should be used for overall status, nor any exclusions. Usage is only implied by the word 'bulk 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