Skip to main content
Glama
aikts

Yandex Tracker MCP

Create Issue

issue_create

Create a new issue in a Yandex Tracker queue with a queue key and summary. Optionally specify type, description, assignee, priority, and additional fields.

Instructions

Create a new issue in a Yandex Tracker queue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queueYesQueue key where to create the issue (e.g., 'MYQUEUE')
summaryYesIssue title/summary
typeNoIssue type id (from get_issue_types tool)
descriptionNoIssue description
assigneeNoAssignee login or UID
priorityNoPriority key (from get_priorities tool,)
fieldsNoAdditional fields to set during issue creation. IMPORTANT: Before creating an issue, you MUST call `queue_get_fields` to get available fields (it returns both global and local fields by default). Fields with schema.required=true are mandatory and must be provided. Use the field's `id` property as the key in this map (e.g., {'fieldId': 'value'}).

Output Schema

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

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

Annotations indicate readOnlyHint=false, consistent with creation. However, the description adds no extra behavioral details (e.g., permissions, side effects, rate limits) beyond what annotations imply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise and front-loaded. However, it may be too terse for a tool with 7 parameters; a bit more context would improve without harming conciseness.

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

Completeness2/5

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

Output schema exists, so return values are covered. But the description fails to mention prerequisites (e.g., calling queue_get_fields for the 'fields' parameter) or provide overall workflow context, leaving gaps.

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 parameters are already documented. The description adds no additional meaning or context beyond the schema, achieving baseline adequacy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a new issue in Yandex Tracker, identifying the verb and resource. It's distinct from sibling tools (e.g., issue_update) but doesn't emphasize the scope or differentiate from other creation tools.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, no prerequisites mentioned despite the complex 'fields' parameter requiring prior calls to queue_get_fields. Lacks any 'when not to use' context.

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