Skip to main content
Glama
aikts

Yandex Tracker MCP

Get Issue Templates

issue_templates_get_all
Read-only

Retrieve Yandex Tracker issue templates, optionally scoped to a queue, to see the correct structure before creating an issue.

Instructions

Get the issue templates (in russian - 'шаблоны задач') configured in Yandex Tracker, optionally scoped to a queue - read one before issue_create instead of inventing a structure. The issue body is in fieldTemplates.description; the template's own description describes the template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number to return, default is None which means to retrieve all pages. Specify page number to retrieve a specific page when context limit is reached.
queueNoOptional queue (Project ID) to scope the result to, like 'SOMEPROJECT'. Templates that are not bound to any queue are usable everywhere and are returned as well.
per_pageNoThe number of items per page. May be decreased if results exceed context window. If there is a change in per_page argument - retrieval must be started over with page = 1, as the paging could have changed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsNoTotal items matching the request, across all pages. Null if unknown or filtered - then page on until a page comes back empty.
pagesNoTotal pages at the requested `per_page`; this is the last page when it equals `page`. Null together with `hits`.
valuesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses that the issue body lives in fieldTemplates.description and clarifies that the template's own description describes the template. This provides meaningful behavioral context not present in annotations or 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 compact, front-loaded with the primary action, and every clause adds value: scope, usage intent, and field guidance. The Russian translation is a minor but harmless addition.

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 list tool with full schema documentation, annotations, and an output schema, the description covers why and when to use it, how to handle queue scoping, and what the key output field means. Nothing essential is missing.

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 coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds context about queue scoping and the relationship between templates and issue creation, but it does not significantly elaborate on parameter details beyond the schema.

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 the tool retrieves issue templates configured in Yandex Tracker, supports optional queue scoping, and explains its purpose as a precursor to issue_create. This distinguishes it from the singular sibling issue_template_get and from comment templates.

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?

It explicitly tells the agent to read templates before calling issue_create instead of inventing a structure, giving strong usage context. It does not explicitly list exclusions or compare against the singular template tool, but the guidance is sufficiently clear.

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