Yandex Tracker MCP

Overview Schema Source Related Servers Discussions Admin

Get Queue Metadata

queue_get_metadata

Read-only

Retrieve detailed metadata for a Yandex Tracker queue: name, description, default type/priority, and expanded sections. Use issueTypesConfig to get resolutions for closing issues.

Instructions

Get detailed metadata about a specific Yandex Tracker queue: name, description, default type and priority, plus the sections named in expand (issue types with their resolutions, workflows, team, ...). Use expand=['issueTypesConfig'] for the resolutions issue_close needs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`expand`	No	Optional list of fields to expand in the response. Available options: 'all', 'projects', 'components', 'versions', 'types', 'team', 'workflows', 'fields', 'issueTypesConfig'. Use 'issueTypesConfig' to get available resolutions for each issue type. A requested section that the queue has nothing in comes back as an empty list.
`queue_id`	Yes	Queue (Project ID) to search in, like 'SOMEPROJECT'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`key`	No
`name`	No
`defaultType`	No
`description`	No
`defaultPriority`	No
`issueTypesConfig`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.8.0Aug 21, 2026

changedInput schema / properties / expand / description

Previous value: -"Optional list of fields to expand in the response. Available options: 'all', 'projects', 'components', 'versions', 'types', 'team', 'workflows', 'fields', 'issueTypesConfig'. Use 'issueTypesConfig' to get available resolutions for each issue type."New value: +"Optional list of fields to expand in the response. Available options: 'all', 'projects', 'components', 'versions', 'types', 'team', 'workflows', 'fields', 'issueTypesConfig'. Use 'issueTypesConfig' to get available resolutions for each issue type. A requested section that the queue has nothing in comes back as an empty list."

addedOutput schema / additionalProperties
```
Added value: +true
```

Addedv0.6.3May 12, 2026

TDQS

A4/5.0

Behavior3/5

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

The readOnlyHint annotation already communicates that this is a safe read operation. The description adds context about the kind of metadata returned and the expand behavior, but it does not disclose deeper behavioral details such as response size limits or failure modes. This is acceptable given the annotation and output schema.

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 two concise sentences with no filler. The core purpose is front-loaded, followed by a practical parameter tip. Every clause earns its place.

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

Completeness5/5

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

For a read-only metadata tool with only two parameters, full schema coverage, and an output schema, the description covers everything needed to select and invoke it correctly. It explains the main purpose, the expand parameter's role, and the relevant integration with issue_close.

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 the baseline is 3. The description adds value by explaining that `expand` controls which metadata sections come back and explicitly ties `issueTypesConfig` to what `issue_close` needs, which is more than the schema alone provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool gets detailed metadata for a specific Yandex Tracker queue and lists what is included (name, description, default type/priority, expandable sections). It distinguishes itself from sibling tools like queues_get_all by emphasizing 'specific queue' and 'detailed metadata', though it does not explicitly name sibling alternatives.

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 description provides concrete usage context and even cross-tool guidance: 'Use expand=[\'issueTypesConfig\'] for the resolutions issue_close needs.' It does not explicitly state when not to use this tool or compare directly to sibling queue tools, but the intended use case is clear.

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

Deploy Server