Skip to main content
Glama
APonkratov

Yandex Tracker MCP Server

by APonkratov

Add Issue Comment

issue_add_comment

Add a comment to a Yandex Tracker issue. Use the summonees parameter to invite users and send notifications, instead of relying on @mentions in the text.

Instructions

Add a comment to a Yandex Tracker issue. IMPORTANT: If you need to mention/call people to the discussion (so they get notifications), do NOT rely on '@login' in the text — use the summonees parameter instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesComment text (markdown supported by Tracker).
issue_idYesIssue ID in the format '<project>-<id>', like 'SOMEPROJECT-1'
summoneesNoOptional list of summoned users (logins or IDs). These users will be invited to the discussion and receive notifications (this is the API way to 'mention/call' someone in Yandex Tracker comments).
markup_typeNoOptional markup type for comment text. Use 'md' for YFM (markdown).
maillist_summoneesNoOptional list of mailing lists to summon (emails). Example: ['team@example.com'].
is_add_to_followersNoWhether to add the comment author to issue followers. Default: true.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
textNo
longIdNo
textHtmlNo
createdAtNo
createdByNo
summoneesNo
transportNo
updatedAtNo
updatedByNo
maillistSummoneesNo
Behavior4/5

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

With only readOnlyHint=false, the description adds valuable behavioral context: @login mentions do not trigger notifications, and summonees must be used instead. This goes beyond the annotation but does not disclose other side effects like follower changes (which are covered in the 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?

Two focused sentences: the first states the tool's purpose, the second delivers the critical usage warning. No fluff, front-loaded, and every sentence earns its place.

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

Completeness4/5

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

For a comment-creation tool with a complete schema and output schema, the description covers the essential purpose and the key gotcha. It lacks details on prerequisites or auth, but those are not necessary given the tool's simplicity and schema coverage.

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 baseline is 3. The description adds extra semantics for the summonees parameter by warning about @login behavior, which is not explicit in the schema. This elevates the parameter meaning beyond the property descriptions.

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 'Add a comment to a Yandex Tracker issue' with a specific verb and resource. It distinguishes from siblings like issue_update_comment and issue_delete_comment by the action 'add'.

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 an explicit 'IMPORTANT' guideline: do not rely on '@login' in text to mention people; use the `summonees` parameter instead. This is a clear when-not/alternative instruction, though it does not contrast this tool with sibling comment-editing tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/APonkratov/yandex-tracker-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server