Skip to main content
Glama
Sign In
Yandex Tracker MCP

Yandex Tracker MCP

by aikts
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get Comment Templates

comment_templates_get_all
Read-only

Fetch reusable Yandex Tracker comment templates, filtered by queue if needed, with pagination support, to review wording and summoned users and mailing lists before adding a comment.

Instructions

Get the comment templates configured in Yandex Tracker - the wording a team reuses when replying, with the users and mailing lists such a comment summons. Read one before adding a comment. Pass queue for the templates of that queue plus those bound to no queue. All pages are fetched by default; pass page for a single one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "comment_templates_get_all"
  }
}

Input 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

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral detail: all pages are fetched by default, passing page returns a single page, and templates bound to no queue are included when queue is provided. This goes beyond the annotation without contradicting it.

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?

Three short sentences with no filler: purpose first, usage context second, pagination behavior third. Every sentence contributes new, actionable information.

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?

The definition is complete for a read-only listing tool. It covers purpose, usage timing, queue scoping, and pagination; the output schema handles return-value documentation, and the annotation covers safety. No critical guidance is missing.

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 the queue fallback behavior and reinforcing the default all-pages behavior for the page parameter, which helps an agent choose parameters correctly even when skimming the schema.

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 identifies the resource: comment templates configured in Yandex Tracker, including their content and associated users/mailing lists. It is a specific verb+resource statement, though it does not explicitly differentiate itself from the sibling comment_template_get beyond the plural 'get_all' framing.

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 gives practical context: 'Read one before adding a comment' tells the agent when this tool matters, and the queue guidance clarifies scoping. It stops short of explicitly naming alternatives or exclusion criteria, so it does not earn 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