Skip to main content
Glama
aikts

Yandex Tracker MCP

Add Issue Comment

issue_add_comment

Add a comment to a Yandex Tracker issue. Optionally summon users or mailing lists to receive notifications.

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
issue_idYesIssue ID in the format '<project>-<id>', like 'SOMEPROJECT-1'
textYesComment text (markdown supported by Tracker).
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).
maillist_summoneesNoOptional list of mailing lists to summon (emails). Example: ['team@example.com'].
markup_typeNoOptional markup type for comment text. Use 'md' for YFM (markdown).
is_add_to_followersNoWhether to add the comment author to issue followers. Default: true.

Output Schema

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

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

The description confirms the write operation (consistent with readOnlyHint=false) and adds behavioral nuance about notification handling via summonees. It could mention side effects like automatic following (covered by parameter) but overall adds value.

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 extremely concise: two sentences that front-load the purpose and then add a critical warning. No wasted words.

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?

Given the presence of an output schema and complete parameter descriptions, the description provides sufficient context for the tool's use. The warning about notifications addresses a common pitfall.

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?

The schema already provides comprehensive descriptions for all 6 parameters (100% coverage). The description adds contextual emphasis on the `summonees` parameter's purpose versus @mention, which helps avoid misuse.

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 title and description clearly state that the tool adds a comment to a Yandex Tracker issue. However, it does not distinguish itself from sibling tools like issue_update_comment or issue_get_comments.

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 important guideline about using the `summonees` parameter instead of '@login' for notifications. It does not explicitly state when to use this tool versus alternatives like issue_update_comment.

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/aikts/yandex-tracker-mcp'

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