Skip to main content
Glama
DChuhin

Yandex Tracker MCP Server

by DChuhin

search_issues

Search issues in Yandex Tracker using YQL query language for complex filters that standard listing cannot handle.

Instructions

Searches issues using a raw Yandex Tracker Query Language (YQL) string. Use for complex filters that list_issues cannot express. Example query: 'Queue: BACK AND Status: Open AND Tags: backend'. Prefer list_issues for simple cases.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided; description does not disclose safety/behavior (e.g., read-only, error handling) beyond YQL usage.

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 sentences plus example, no wasted words, front-loaded with key info.

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?

Covers main usage with examples and sibling distinction, but lacks mention of search_issues_scroll and pagination details.

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 coverage 0%; description explains query with an example but does not mention limit 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?

Clearly states it searches issues using YQL, distinguishes from list_issues by noting complex filters.

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 says when to use (complex filters) and when to prefer list_issues (simple cases), with an example query.

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

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/DChuhin/tracker-mcp-server'

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