Yandex Tracker MCP

Overview Schema Related Servers Score Discussions

Get Issue Comments

issue_get_comments

Read-only

Get comments for a Yandex Tracker issue by its ID, with pagination via cursor. Fetch next pages by passing the returned next_cursor value.

Instructions

Get a page of comments of a Yandex Tracker issue by its id. Returns the comments plus 'next_cursor'. To fetch the next page, pass 'next_cursor' from the previous result as the 'cursor' argument; when 'next_cursor' is null there are no more comments.

Input Schema

TableJSON Schema

Name	Required	Description
`cursor`	No	Cursor for the next page of comments: the 'next_cursor' value returned by the previous call. Leave empty for the first page.
`fields`	No	Fields to include in each comment. In order to not pollute the context window - select only the fields you need (comment text/text_html can be large). Not specifying this returns all available fields.
`issue_id`	Yes	Issue ID in the format '<project>-<id>', like 'SOMEPROJECT-1'
`per_page`	No	The number of items per page for cursor-paginated endpoints. May be decreased if results exceed the context window.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`comments`	Yes
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed10 schema fields changedv0.8.0Aug 21, 2026

addedInput schema / $defs

Added value: +{
+  "CommentFieldsEnum": {
+    "enum": [
+      "created_at",
+      "updated_at",
+      "created_by",
+      "updated_by",
+      "id",
+      "long_id",
+      "text",
+      "transport",
+      "text_html",
+      "summonees",
+      "maillist_summonees"
+    ],
+    "title": "CommentFieldsEnum",
+    "type": "string"
+  }
+}

addedInput schema / properties / cursor

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Cursor for the next page of comments: the 'next_cursor' value returned by the previous call. Leave empty for the first page.",
+  "title": "Cursor"
+}

addedInput schema / properties / fields

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/CommentFieldsEnum"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Fields to include in each comment. In order to not pollute the context window - select only the fields you need (comment text/text_html can be large). Not specifying this returns all available fields.",
+  "title": "Fields"
+}

addedInput schema / properties / per_page

Added value: +{
+  "default": 50,
+  "description": "The number of items per page for cursor-paginated endpoints. May be decreased if results exceed the context window.",
+  "minimum": 1,
+  "title": "Per Page",
+  "type": "integer"
+}

addedOutput schema / description

Added value: +"A page of comments plus the cursor to fetch the next page.\n\n`next_cursor` is the cursor for the next page, or `None` when there are no more\npages; how it is obtained depends on the endpoint. Pass it back as the `cursor`\nargument to continue."

addedOutput schema / properties / comments

Added value: +{
+  "items": {
+    "$ref": "#/$defs/IssueComment"
+  },
+  "title": "Comments",
+  "type": "array"
+}

addedOutput schema / properties / next_cursor

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Next Cursor"
+}

removedOutput schema / properties / result

Removed value: -{
-  "items": {
-    "$ref": "#/$defs/IssueComment"
-  },
-  "title": "Result",
-  "type": "array"
-}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "comments"
+]

changedOutput schema / title

Previous value: -"issue_get_commentsOutput"New value: +"CommentsPage"

Changed3 schema fields changedv0.6.3May 12, 2026

addedOutput schema / $defs / IssueComment / properties / maillistSummonees

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/MaillistReference"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Maillistsummonees"
+}

addedOutput schema / $defs / IssueComment / properties / summonees

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/UserReference"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Summonees"
+}

addedOutput schema / $defs / MaillistReference

Added value: +{
+  "properties": {
+    "display": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Display"
+    },
+    "id": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Id"
+    }
+  },
+  "title": "MaillistReference",
+  "type": "object"
+}

First observedv1.0.0Aug 15, 2025

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, so the description adds value by explaining the pagination mechanism: it returns 'next_cursor' and instructs how to use it to fetch subsequent pages, including the terminal condition (null when no more). This beyond-annotation context is critical for correct usage and aligns with the read-only annotation.

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 sentences, front-loaded with the purpose, and contains no redundant information. Every sentence adds value: the first defines the action, the second explains pagination. It is concise and well-structured.

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 description covers the essential aspects for correct use: it identifies the target, explains pagination, and indicates the return includes comments plus a cursor. The output schema (which exists) likely defines the comment structure, so the description doesn't need to repeat that. The tool's complexity (pagination, multiple parameters) is sufficiently addressed for a read-only operation with 100% schema parameter descriptions.

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?

The schema description coverage is 100%, meaning every parameter (cursor, fields, issue_id, per_page) already has a detailed description in the input schema. The description does not add new meaning to individual parameters beyond what the schema states; it merely summarizes the pagination flow. According to the rubric, when coverage is high, the description can earn a baseline of 3, which is appropriate here.

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's purpose: 'Get a page of comments of a Yandex Tracker issue by its id.' It uses a specific verb ('Get'), identifies the resource ('comments'), and mentions the required id. This distinguishes it from sibling tools that handle other aspects of issues (links, worklogs, etc.) and explicitly describes the pagination behavior, which is a key feature.

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 clear context on how to use it: it retrieves comments and includes pagination instructions ('pass 'next_cursor'...'). It does not explicitly mention when not to use it or alternatives, but since there is no other comment-retrieval tool among siblings, it is implicitly the correct choice for reading comments. The guidance is adequate but could be more explicit about exclusions.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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