Skip to main content
Glama
imdeniil

ya-tracker-mcp

by imdeniil

create_issue

Create a new issue in Yandex Tracker by providing queue and summary, with optional fields for assignee, priority, tags, parent issue, and description.

Instructions

Create a new issue in Yandex Tracker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoList of tags
queueYesQueue key (e.g. "DEV")
fieldsNoOptional list of fields to show in response. Use ["all"] for all fields.
parentNoParent issue key (e.g. "DEV-123")
sprintNoSprint ID
projectNoProject shortId (number)
summaryYesIssue title (max 255 chars)
assigneeNoAssignee login
deadlineNoDeadline date (YYYY-MM-DD)
priorityNoPriority key: "blocker", "critical", "normal", "minor", "trivial"
followersNoList of follower logins
issue_typeNoIssue type key: "task", "bug", "story", "epic"
descriptionNoIssue description (YFM markdown supported)
extra_fieldsNoAdditional/custom/local fields as dict (e.g. {"coAssignees": ["user1"], "myCustomField": "value"})
story_pointsNoStory points estimate
output_formatNoResponse format: "text" (default, markdown) or "json"text
full_descriptionNoIf true, do not truncate description (default false)
original_estimationNoOriginal estimation in ISO 8601 (e.g. "PT2H", "P1D")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only states the action ('create a new issue') without mentioning side effects, required permissions, or return behavior. It does not add value beyond what the tool's name implies.

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 a single, direct sentence with no redundant or extraneous content. It is appropriately front-loaded and wastes no words, maximizing 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?

With 18 parameters, no annotations, and a one-sentence description, the tool lacks sufficient context for an agent to know when or how to invoke it effectively. The output schema exists, but the description does not address required fields, use cases, or integration with other tools, making it incomplete for a tool of this complexity.

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?

The input schema has 100% description coverage for all 18 parameters, so the baseline is 3. The description does not add any parameter semantics beyond the schema, but it does not need to since the schema fully documents each parameter.

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 tool's function: 'Create a new issue in Yandex Tracker.' This uses a specific verb ('create') and resource ('issue'), and distinguishes it from sibling tools like update_issue, search_issues, and delete_macro by focusing on the creation action.

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?

The description provides no guidance on when to use this tool versus alternatives, such as import_issue or create_from_preset. It lacks any context about prerequisites, typical use cases, or conditions under which another tool would be more appropriate.

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/imdeniil/ya-tracker-mcp'

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