Skip to main content
Glama
aikts

Yandex Tracker MCP

Get All Queues

queues_get_all
Read-only

Retrieve all Yandex Tracker queues accessible to you, with optional pagination to manage large result sets. Use fields to limit response data.

Instructions

Find all Yandex Tracker queues available to the user (a queue is a project in some sense). page defaults to None and fetches ALL pages; pass a page number only when the result does not fit the context window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number to return, default is None which means to retrieve all pages. Specify page number to retrieve a specific page when context limit is reached.
fieldsNoFields to include in the response; omitting returns ALL of them (unlike project_find/portfolio_find/goal_find, which default to a small subset). key and name are usually enough.
per_pageNoThe 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsNoTotal items matching the request, across all pages. Null if unknown or filtered - then page on until a page comes back empty.
pagesNoTotal pages at the requested `per_page`; this is the last page when it equals `page`. Null together with `hits`.
valuesNo

Schema Changelog

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

  1. Changed1 schema field changedv0.10.0
    • changedInput schema / properties / fields / description
      Previous value: -"Fields to include in the response. In order to not pollute context window - select appropriate fields beforehand. Not specifying fields returns ALL available fields (unlike project_find/portfolio_find/goal_find, which default to a small field subset). Most of the time one needs key and name only."New value: +"Fields to include in the response; omitting returns ALL of them (unlike project_find/portfolio_find/goal_find, which default to a small subset). key and name are usually enough."
  2. Changed9 schema fields changedv0.8.0
    • changedInput schema / properties / fields / description
      Previous value: -"Fields to include in the response. In order to not pollute context window - select appropriate fields beforehand. Not specifying fields will return all available. Most of the time one needs key and name only."New value: +"Fields to include in the response. In order to not pollute context window - select appropriate fields beforehand. Not specifying fields returns ALL available fields (unlike project_find/portfolio_find/goal_find, which default to a small field subset). Most of the time one needs key and name only."
    • changedInput schema / properties / page / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / $defs / Queue / additionalProperties
      Added value: +true
    • addedOutput schema / properties / hits
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Total items matching the request, across all pages. Null if unknown or filtered - then page on until a page comes back empty.",
      +  "title": "Hits"
      +}
    • addedOutput schema / properties / pages
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Total pages at the requested `per_page`; this is the last page when it equals `page`. Null together with `hits`.",
      +  "title": "Pages"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "items": {
      -    "$ref": "#/$defs/Queue"
      -  },
      -  "title": "Result",
      -  "type": "array"
      -}
    • addedOutput schema / properties / values
      Added value: +{
      +  "items": {
      +    "$ref": "#/$defs/Queue"
      +  },
      +  "title": "Values",
      +  "type": "array"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
    • changedOutput schema / title
      Previous value: -"queues_get_allOutput"New value: +"PaginatedResult[Queue]"
  3. Changed11 schema fields changedv0.6.3
    • addedInput schema / $defs
      Added value: +{
      +  "QueueFieldsEnum": {
      +    "enum": [
      +      "id",
      +      "key",
      +      "name",
      +      "description",
      +      "defaultType",
      +      "defaultPriority",
      +      "issueTypesConfig"
      +    ],
      +    "title": "QueueFieldsEnum",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / fields
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "$ref": "#/$defs/QueueFieldsEnum"
      +      },
      +      "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. Most of the time one needs key and name only.",
      +  "title": "Fields"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Page number to return, default is None which means to retrieve all pages. Specify page number to retrieve a specific page when context limit is reached.",
      +  "title": "Page"
      +}
    • addedInput schema / properties / per_page
      Added value: +{
      +  "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"
      +}
    • addedOutput schema / $defs / Queue / properties / id / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / $defs / Queue / properties / id / default
      Added value: +null
    • removedOutput schema / $defs / Queue / properties / id / type
      Removed value: -"integer"
    • addedOutput schema / $defs / Queue / properties / issueTypesConfig
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "$ref": "#/$defs/QueueIssueTypeConfig"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Issuetypesconfig"
      +}
    • removedOutput schema / $defs / Queue / required
      Removed value: -[
      -  "id"
      -]
    • addedOutput schema / $defs / QueueIssueTypeConfig
      Added value: +{
      +  "description": "Issue type configuration within a queue, including available resolutions.",
      +  "properties": {
      +    "issueType": {
      +      "anyOf": [
      +        {
      +          "$ref": "#/$defs/IssueTypeReference"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Issue type reference"
      +    },
      +    "resolutions": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "$ref": "#/$defs/Resolution"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Available resolutions for this issue type",
      +      "title": "Resolutions"
      +    }
      +  },
      +  "title": "QueueIssueTypeConfig",
      +  "type": "object"
      +}
    • addedOutput schema / $defs / Resolution
      Added value: +{
      +  "properties": {
      +    "description": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Resolution description",
      +      "title": "Description"
      +    },
      +    "id": {
      +      "description": "Unique resolution identifier",
      +      "title": "Id",
      +      "type": "integer"
      +    },
      +    "key": {
      +      "description": "Resolution key",
      +      "title": "Key",
      +      "type": "string"
      +    },
      +    "name": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Displayed resolution name",
      +      "title": "Name"
      +    },
      +    "order": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Display weight for ordering resolutions",
      +      "title": "Order"
      +    },
      +    "version": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Resolution version",
      +      "title": "Version"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "key"
      +  ],
      +  "title": "Resolution",
      +  "type": "object"
      +}
  4. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true, so the read-only nature is covered. The description adds useful behavioral context beyond that: the default behavior of fetching ALL pages, the context-window consideration, and that the result is scoped to queues available to the user. This is valuable because page semantics can otherwise be surprising.

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 two short sentences with the purpose front-loaded and pagination guidance immediately after. Every sentence earns its place, and the parenthetical about queues being projects adds useful domain context without bloating the text.

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

Completeness5/5

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

Given the readOnlyHint annotation, the extensive schema descriptions, and the presence of an output schema, the description covers the essential operational guidance: what the tool returns, its scope, and how to handle pagination when context limits are hit. Nothing critical is missing for an agent to call it correctly.

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%, and the schema already thoroughly documents page, fields, and per_page, including defaults and the restart-on-per_page-change caveat. The tool description repeats the page default but adds little beyond the schema, so the baseline of 3 applies.

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 states a specific action and resource: 'Find all Yandex Tracker queues available to the user.' It clearly distinguishes this list-all operation from sibling tools like queue_get_metadata or queue_get_components by emphasizing scope ('all queues available to the user') and the pagination behavior tied to fetching all pages.

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

Usage Guidelines4/5

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

The description gives clear context for when to use the page parameter: only pass a page number when the result does not fit the context window; otherwise fetch all pages. It does not explicitly name alternatives or when-not-to-use the tool versus siblings, but the pagination guidance is actionable and unambiguous.

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/aikts/yandex-tracker-mcp'

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