Yandex Tracker MCP

{ "$defs": { "IssueFieldsEnum": { "enum": [ "created_at", "updated_at", "created_by", "updated_by", "unique", "key", "summary", "description", "type", "priority", "assignee", "status", "previous_status", "deadline", "components", "start", "story_points", "tags", "votes", "sprint", "epic", "parent" ], "title": "IssueFieldsEnum", "type": "string" } }, "properties": { "fields": { "anyOf": [ { "items": { "$ref": "#/$defs/IssueFieldsEnum" }, "type": "array" }, { "type": "null" } ], "default": null, "description": "Fields to include in the response. In order to not pollute context window - select appropriate fields beforehand. Not specifying fields will return all available.", "title": "Fields" }, "include_description": { "default": false, "description": "Whether to include issue description in the issues result. It can be large, so use only when needed.", "title": "Include Description", "type": "boolean" }, "page": { "default": 1, "description": "Page number to return, default is 1", "minimum": 1, "title": "Page", "type": "integer" }, "per_page": { "default": 100, "description": "The number of items per page. May be decreased if results exceed context window. If there is a change in per_page argument - retrieval must be started over with page = 1, as the paging could have changed.", "minimum": 1, "title": "Per Page", "type": "integer" }, "query": { "description": "Search query to filter issues using Yandex Tracker Query.\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 not resolved (open, in progress) issues: `\"Resolution\": unresolved()`\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\"`\nComplete instructions page is available here: https://yandex.ru/support/tracker/ru/user/query-filter\n", "title": "Query", "type": "string" } }, "required": [ "query" ], "title": "issues_findArguments", "type": "object" }