Skip to main content
Glama
aikts

Yandex Tracker MCP

by aikts
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

Get Issue Attachments

issue_get_attachments
Read-only

Retrieve attachments from a Yandex Tracker issue by its ID. Select only needed fields to avoid loading large content.

Instructions

Get attachments of a Yandex Tracker issue by its id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoFields to include in each attachment; omit to get all. The 'content' field can be large, so select only what you need.
issue_idYesIssue ID in the format '<project>-<id>', like 'SOMEPROJECT-1'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

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 attachment. In order to not pollute the context window - select only the fields you need (the 'content' field can be large). Not specifying this returns all available fields."New value: +"Fields to include in each attachment; omit to get all. The 'content' field can be large, so select only what you need."
  2. Changed2 schema fields changedv0.8.0
    • addedInput schema / $defs
      Added value: +{
+  "AttachmentFieldsEnum": {
+    "enum": [
+      "created_at",
+      "created_by",
+      "id",
+      "name",
+      "content",
+      "size",
+      "mimetype",
+      "metadata"
+    ],
+    "title": "AttachmentFieldsEnum",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / fields
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/AttachmentFieldsEnum"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Fields to include in each attachment. In order to not pollute the context window - select only the fields you need (the 'content' field can be large). Not specifying this returns all available fields.",
+  "title": "Fields"
+}
  3. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

The readOnlyHint annotation already covers the safety profile, so the description does not need to restate read-only behavior. The description adds no behavioral context beyond 'by its id' and does not discuss pagination, size limits, or potential for large content, though the schema's fields parameter does warn about the content field.

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 one short sentence with no filler, front-loads the action and resource, and is easily parsable. Every word contributes meaning.

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 simple read-only attachment-listing tool, the description combined with the rich input schema, readOnlyHint, and output schema is sufficient. The required input is clear, the optional fields behavior is documented in the schema, and no critical invocation information is missing.

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%, so both issue_id and fields are already documented in the input schema. The description reinforces that issue_id identifies the target issue but adds no new semantic value beyond the parameter 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 states a specific verb ('Get'), a clear resource ('attachments'), and the required identifier ('by its id'). This distinguishes it from sibling issue_get_* tools such as issue_get_comments, issue_get_worklogs, and issue_get, since 'attachments' is an unambiguous resource.

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

Usage Guidelines3/5

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

The description implies the tool is used when a caller needs attachments for a specific Yandex Tracker issue, and the issue ID requirement is clear. However, it does not explicitly state when to prefer this over alternatives or mention any exclusions, leaving differentiation to inference from the tool name and sibling list.

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