Skip to main content
Glama
aikts

Yandex Tracker MCP

Get Issue Comments

issue_get_comments
Read-only

Fetch comments for a Yandex Tracker issue by ID. Use the returned cursor to paginate through all comments until null.

Instructions

Get a page of comments of a Yandex Tracker issue by its id. Returns the comments plus next_cursor - pass it back as cursor until it is null.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoCursor for the next page of comments: the 'next_cursor' value returned by the previous call. Leave empty for the first page.
fieldsNoFields to include in each comment; omit to get all. text/text_html can be large, so select only what you need.
issue_idYesIssue ID in the format '<project>-<id>', like 'SOMEPROJECT-1'
per_pageNoThe number of items per page for cursor-paginated endpoints. May be decreased if results exceed the context window.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
commentsYes
next_cursorNo

Schema Changelog

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

  1. Changed1 schema field changedv0.10.0
    • changedInput schema / properties / fields / description
      Previous value: -"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."New value: +"Fields to include in each comment; omit to get all. text/text_html can be large, so select only what you need."
  2. Changed10 schema fields changedv0.8.0
    • 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"
  3. Changed3 schema fields changedv0.6.3
    • 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"
      +}
  4. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations provide readOnlyHint=true. The description adds meaningful behavioral context: results are paginated, the response includes next_cursor, and callers must loop by passing next_cursor back as cursor until null. This goes beyond the static annotation and clarifies the expected interaction pattern.

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 sentences with no redundancy. The core purpose is front-loaded, and the pagination instruction is the only additional sentence, earning its place.

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?

Combined with a fully described input schema, an output schema, and readOnlyHint annotation, the description provides everything needed to correctly invoke and paginate through comments. No critical behavioral or usage detail 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% with detailed parameter descriptions, so the baseline is 3. The description adds value by connecting 'next_cursor' from the response to the 'cursor' parameter, explaining the pagination workflow that ties parameters together across calls.

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?

States a specific action ('Get a page of comments') on a specific resource ('a Yandex Tracker issue by its id'). Clearly distinguishes from sibling tools like issue_get_worklogs or issue_get_attachments by naming the exact resource.

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?

Clear context: this is the tool for fetching issue comments, identified by issue_id. It does not explicitly name alternatives or exclusions, but the resource specificity makes the intended use unambiguous. The pagination instruction ('pass it back as cursor until it is null') also guides multi-page usage.

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

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