Yandex Tracker MCP

Overview Schema Source Related Servers Discussions Admin

Get Issue

issue_get

Read-only

Retrieve a Yandex Tracker issue by its key and get the full record, including current version. Use when you need a specific task's complete details.

Instructions

Read one Yandex Tracker issue (task, ticket, bug; in russian - 'задача') by its key and return its full record, the current version included. To search instead, use issues_find. Comments, links, attachments, worklogs, checklist, changelog and transitions each have their own issue_get_* tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`issue_id`	Yes	Issue ID in the format '<project>-<id>', like 'SOMEPROJECT-1'
`include_description`	No	Whether to include issue description in the issues result. It can be large, so use only when needed.

Output Schema

TableJSON Schema

Name	Required	Description
`key`	No
`epic`	No
`tags`	No
`type`	No
`spent`	No
`start`	No
`votes`	No
`boards`	No	Agile boards the issue shows up on. Tracker fills this in from the boards' own filters - an issue is not assigned to a board directly, so this is read-only. Use the board id with `board_get`, `board_get_columns` or `board_get_sprints`.
`parent`	No
`sprint`	No	Sprints the issue is in. Use `board_get_sprints` to look up the sprints of a board, and pass a sprint id to `issue_update` to move the issue between them.
`status`	No
`unique`	No
`summary`	No
`version`	No
`assignee`	No
`deadline`	No
`priority`	No
`createdAt`	No
`createdBy`	No
`updatedAt`	No
`updatedBy`	No
`components`	No
`estimation`	No
`description`	No
`storyPoints`	No
`previousStatus`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.10.0Sep 6, 2026

addedOutput schema / $defs / IssueBoardReference

Added value: +{
+  "description": "A board an issue shows up on, as nested in an issue record.\n\nTracker spells this one differently from its other references: `name`\ninstead of `display`, and a numeric id. That id is what `board_get`,\n`board_get_columns` and `board_get_sprints` take.",
+  "properties": {
+    "id": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Board identifier, as taken by the `board_get`, `board_get_columns` and `board_get_sprints` tools",
+      "title": "Id"
+    },
+    "name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Board name",
+      "title": "Name"
+    }
+  },
+  "title": "IssueBoardReference",
+  "type": "object"
+}

addedOutput schema / properties / boards

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/IssueBoardReference"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Agile boards the issue shows up on. Tracker fills this in from the boards' own filters - an issue is not assigned to a board directly, so this is read-only. Use the board id with `board_get`, `board_get_columns` or `board_get_sprints`.",
+  "title": "Boards"
+}

addedOutput schema / properties / sprint / description

Added value: +"Sprints the issue is in. Use `board_get_sprints` to look up the sprints of a board, and pass a sprint id to `issue_update` to move the issue between them."

Changed4 schema fields changedv0.6.3May 12, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

addedOutput schema / properties / estimation

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

addedOutput schema / properties / spent

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

addedOutput schema / properties / version

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Version"
+}

First observedv1.0.0Aug 15, 2025

TDQS

A4.5/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 consistently describes a read operation. It adds useful behavioral context by stating that the tool returns the full issue record including the current version, which goes beyond the schema's parameter documentation.

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 concise sentences with no filler. The core purpose is front-loaded, and the routing to alternatives is packed efficiently into the second sentence.

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?

For a read-only tool with a readOnlyHint annotation, an output schema, fully described parameters, and explicit sibling differentiation, nothing essential is missing. The description covers purpose, scope, and alternatives without redundancy.

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?

Schema description coverage is 100%, and both parameters (issue_id and include_description) are fully documented with formats and fine print about size. The tool description does not add meaning beyond the schema, so the baseline of 3 applies.

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?

Description clearly states a specific verb ('Read') and resource ('one Yandex Tracker issue') and notes it returns the full record including version. It also distinguishes itself from issues_find and the issue_get_* subresource tools, so an agent can tell exactly what this tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly directs users to issues_find when searching instead and lists which related resources (comments, links, attachments, worklogs, etc.) have their own issue_get_* tools. This gives clear when-to-use and when-not-to-use guidance with named alternatives.

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

Deploy Server