Skip to main content
Glama

Yandex Tracker MCP

issues_find

Search and filter Yandex Tracker issues by queue, created date, or custom queries using YQL syntax. Retrieve specific issues with precise filtering and sorting options.

Instructions

Find Yandex Tracker issues by queue and/or created date

Input Schema

NameRequiredDescriptionDefault
pageNoPage number to return, default is 1
queryYesSearch query to filter issues using Yandex Tracker Query Language, Instructions: # General instructions 1. To search by a specific field use the following syntax: `Description: "some issue description"` 2. Multiple fields should be separated by space: `Description: "some issue description" Created: today()` 3. If you need to specify multiple values for the same field - provide them using comma (,), e.g.: `author: "vpupkin","iivanov"` 4. You may specify multiple conditions and combine them using `AND` and `OR` statements, e.g. `<param_1>: "<value_1>" AND <param_2>: "<value_2>"` 5. You may use brackets for complex logical expressions 6. To find issues with exact string matching in the field use this syntax: `Summary: #"Version 2.0"`. If you need to pass special characters - you must escape them using `\` symbol 7. To find issues that don't contain the specified text use this syntax: `Summary: !"Version 2.0"`. If you need to pass special characters - you must escape them using `\` symbol 8. If you need to search by local queue field use the following syntax: `<QUEUE>.<LOCAL_FIELD_KEY>: "<value>", where <QUEUE> is a queue key, <LOCAL_FIELD_KEY> is a local field's key from the `queue_get_local_fields` tool result. 9. For dates use the format YYYY-MM-DD. 10. For numerical values you may use comparison operators (>, <, >=, <=): `<param>: ><value>`. 11. To sort the result specify the `Sort By` directive (you may provide ASC or DESC for the sort order): `"Sort By": Created ASC`. # Functions These functions may be used, for example: `Created: week()` - return issues created on the current week" * `empty()` - empty value * `notEmpty()` - not empty value * `now()` - current time * `today()` - current date * `week()` - current week * `month()` - current month * `quarter()` - current quarter * `year()` - current year * `unresolved()` - there is no resolution # Examples Find issues in a specific queue: `"Queue": "PROJ"` Find issues by an assignee: `"Assignee": "Иван Иванов"` Find issues in specific status: `"Status": "Открыт", "В работе"` Find issues created in a specific range: `"Created": "2017-01-01".."2017-01-30"` Find issues created no earlier than 1 week and 1 day before today: `Created: > today() - "1w 1d"`

Input Schema (JSON Schema)

{ "properties": { "page": { "default": 1, "description": "Page number to return, default is 1", "title": "Page", "type": "integer" }, "query": { "description": "Search query to filter issues using Yandex Tracker Query Language, Instructions:\n# General instructions\n1. To search by a specific field use the following syntax: `Description: \"some issue description\"`\n2. Multiple fields should be separated by space: `Description: \"some issue description\" Created: today()`\n3. If you need to specify multiple values for the same field - provide them using comma (,), e.g.: `author: \"vpupkin\",\"iivanov\"`\n4. You may specify multiple conditions and combine them using `AND` and `OR` statements, e.g. `<param_1>: \"<value_1>\" AND <param_2>: \"<value_2>\"`\n5. You may use brackets for complex logical expressions\n6. To find issues with exact string matching in the field use this syntax: `Summary: #\"Version 2.0\"`. If you need to pass special characters - you must escape them using `\\` symbol\n7. To find issues that don't contain the specified text use this syntax: `Summary: !\"Version 2.0\"`. If you need to pass special characters - you must escape them using `\\` symbol\n8. If you need to search by local queue field use the following syntax: `<QUEUE>.<LOCAL_FIELD_KEY>: \"<value>\", where <QUEUE> is a queue key, <LOCAL_FIELD_KEY> is a local field's key from the `queue_get_local_fields` tool result.\n9. For dates use the format YYYY-MM-DD.\n10. For numerical values you may use comparison operators (>, <, >=, <=): `<param>: ><value>`.\n11. To sort the result specify the `Sort By` directive (you may provide ASC or DESC for the sort order): `\"Sort By\": Created ASC`.\n# Functions\nThese functions may be used, for example: `Created: week()` - return issues created on the current week\"\n* `empty()` - empty value\n* `notEmpty()` - not empty value\n* `now()` - current time\n* `today()` - current date\n* `week()` - current week\n* `month()` - current month\n* `quarter()` - current quarter\n* `year()` - current year\n* `unresolved()` - there is no resolution\n# Examples\nFind issues in a specific queue: `\"Queue\": \"PROJ\"`\nFind issues by an assignee: `\"Assignee\": \"Иван Иванов\"`\nFind issues in specific status: `\"Status\": \"Открыт\", \"В работе\"`\nFind issues created in a specific range: `\"Created\": \"2017-01-01\"..\"2017-01-30\"`\nFind issues created no earlier than 1 week and 1 day before today: `Created: > today() - \"1w 1d\"`\n", "title": "Query", "type": "string" } }, "required": [ "query" ], "title": "issues_findArguments", "type": "object" }

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