Yandex Tracker MCP Server

Create Queue Version

queue_create_version

Create a new version in a Yandex Tracker queue, specifying its name, optional dates, and description.

Instructions

Create a new version in a Yandex Tracker queue.

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": {
      "queue_id": "<queue_id>",
      "name": "<name>"
    },
    "name": "queue_create_version"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Version name
`due_date`	No	Optional version due date in YYYY-MM-DD format
`queue_id`	Yes	Queue (Project ID) to search in, like 'SOMEPROJECT'
`start_date`	No	Optional version start date in YYYY-MM-DD format
`description`	No	Optional version description

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`dueDate`	No
`version`	Yes
`archived`	Yes
`released`	Yes
`startDate`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.2Jul 31, 2026

TDQS

B3.3/5.0

Behavior2/5

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

The description simply restates the write nature already indicated by annotations (readOnlyHint=false). It adds nothing about side effects, error behavior, idempotency, or confirmation of creation. Given the annotation, the bar is lower, but the description still fails to provide any additional behavioral context beyond what is already known.

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, clear sentence that conveys the essential action and target. There is no redundancy, filler, or unnecessary detail. It is appropriately sized for the tool's straightforward purpose.

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?

The input schema covers all parameters, annotations indicate a write operation, and an output schema exists, so the basic usage is fully documented. However, the description lacks broader context such as how creating a version interacts with other queue data, whether duplicate names are allowed, or when to use this over other version-related tools. It is minimally adequate but not complete in a holistic sense.

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%, so all parameters are already documented with meaningful descriptions. The tool description adds no additional parameter-level insight, but the schema does the heavy lifting. This matches the baseline for full schema 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 clearly states a specific verb ('Create') and resource ('a new version in a Yandex Tracker queue'), which distinguishes it from sibling tools like queue_get_versions. It is unambiguous and directly conveys the tool's core function.

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?

No guidance is provided on when to use this tool versus alternatives, such as using queue_get_versions to list existing versions or other mutation tools. There is no mention of prerequisites, whether the queue must exist, or when this operation should be preferred over updating an existing version. The description is silent on usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server