Skip to main content
Glama
APonkratov

Yandex Tracker MCP Server

by APonkratov

Update Issue

issue_update

Update an existing Yandex Tracker issue by changing only the specified fields, leaving others untouched. Discover available fields with queue_get_fields before updating.

Instructions

Update an existing Yandex Tracker issue. Only fields that are provided will be updated; omitted fields remain unchanged. Use queue_get_fields to discover available fields before updating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoIssue tags as array of strings.
typeNoIssue type. Object with 'id' (type ID) and/or 'key' (type key like 'bug', 'task'). Use `queue_get_metadata` tool with expand=['issueTypesConfig'] to get available issue types in this queue.
fieldsNoAdditional fields to update. Use queue_get_fields to discover available fields. Use the field's 'id' property as the key (e.g., {'fieldId': 'value'}).
parentNoParent issue reference. Object with 'id' (parent issue ID) and/or 'key' (parent issue key like 'QUEUE-123').
sprintNoSprint assignments. Array of objects, each with 'id' field containing the sprint ID (integer).
projectNoProject assignment. Object with 'primary' (int, main project shortId) and optional 'secondary' (list of ints, additional project shortIds).
summaryNoNew issue title/summary
versionNoIssue version for optimistic locking. Changes are only made to the current version of the issue. Always try to receive issue's version using issue_get tool first.
issue_idYesIssue ID in the format '<project>-<id>', like 'SOMEPROJECT-1'
priorityNoIssue priority. Object with 'id' (priority ID) and/or 'key' (priority key like 'critical', 'normal'). Use get_priorities to find available priorities.
followersNoIssue followers/watchers. Array of objects, each with 'id' field containing the user ID or login.
descriptionNoNew issue description (use markdown formatting)
markup_typeNoMarkup type for description text. Use 'md' for YFM (markdown) markup.md

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNo
epicNo
tagsNo
typeNo
spentNo
startNo
votesNo
parentNo
sprintNo
statusNo
uniqueNo
summaryNo
versionNo
assigneeNo
deadlineNo
priorityNo
createdAtNo
createdByNo
updatedAtNo
updatedByNo
componentsNo
estimationNo
descriptionNo
storyPointsNo
previousStatusNo
Behavior4/5

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

The description adds a key behavioral detail beyond the readOnlyHint annotation: partial updates ('Only fields that are provided will be updated; omitted fields remain unchanged'). This is important for understanding how the tool behaves and aligns with the write operation implied by readOnlyHint=false.

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 long, front-loaded with the core action, and includes a practical prerequisite. Every sentence earns its place with no redundant phrasing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a complex tool with 13 parameters and a rich input schema, the description covers the essential behavior and a pre-requisite action. It does not repeat details already present in the schema (e.g., version locking), and since an output schema exists, return values need not be explained. The description is sufficiently complete.

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 the schema already documents all parameters. The description adds general context that omitted fields remain unchanged, but does not elaborate on individual parameters. This matches the baseline of 3 for high schema coverage.

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 action ('Update'), the resource ('existing Yandex Tracker issue'), and the scope ('only fields that are provided will be updated'). This distinguishes it from sibling tools like issue_create and issue_close, which serve different purposes.

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 a concrete usage guideline: 'Use queue_get_fields to discover available fields before updating.' While it does not explicitly mention alternatives or when-not-to-use cases, the context is clear enough for an agent to know this tool is for updating existing issues.

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

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