Skip to main content
Glama
A1 Yandex KIT MCP

A1 Yandex KIT MCP

List collections

list_collections
Read-only

Retrieve paginated store collections, filtered by type or status, to review manually curated or dynamically generated product sets; use coverage metadata to avoid claiming incomplete results.

Instructions

List collections of the store (paginated). A collection is a curated set of product cards: STATIC (filled manually via manage_collection_cards) or DYNAMIC (filled by filters). The response carries a machine-readable coverage envelope (coverage, received, total_count, pages_read); coverage:"partial" MUST be reflected in the user-facing answer and forbids claiming the listing is complete.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoFetch all pages via auto-pagination, up to 500 items; ignores page/per_page.
pageNoPage number, starting at 1 (default 1).
typeNoFilter by collection type.
fieldsNoCSV columns; only valid together with format:"csv". Field names are validated against the item schema of the operation's response — an unknown name fails with the list of allowed fields. Default: every top-level scalar field of the item.
formatNoOutput format: "csv" renders the items as RFC 4180 CSV (a leading "# coverage:" comment line, then the header row) instead of JSON — cheaper for wide exports. Default: JSON.
statusNoFilter by collection status (default: both ACTIVE and INACTIVE).
per_pageNoItems per page, 1-100 (default 25). Values outside the range are clamped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.1
    • addedInput schema / properties / status / minItems
      Added value: +1
  2. Changed2 schema fields changedv1.6.0
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "CSV columns; only valid together with format:\"csv\". Field names are validated against the item schema of the operation's response — an unknown name fails with the list of allowed fields. Default: every top-level scalar field of the item.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
    • addedInput schema / properties / format
      Added value: +{
      +  "description": "Output format: \"csv\" renders the items as RFC 4180 CSV (a leading \"# coverage:\" comment line, then the header row) instead of JSON — cheaper for wide exports. Default: JSON.",
      +  "enum": [
      +    "csv"
      +  ],
      +  "type": "string"
      +}
  3. First observedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the behavioral load and does so well: it discloses that pagination applies, that the response includes a machine-readable coverage envelope (coverage, received, total_count, pages_read), and that coverage:'partial' must be surfaced and forbids claiming completeness. That is meaningful operational context beyond the annotations, though it stops short of describing ordering or per-page defaults.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action, then resource definition, then the response-coverage contract. Dense but each sentence carries distinct information; the parenthetical envelope field list is slightly heavy but earns its place given there is no output schema.

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?

For a 7-parameter, zero-required, read-only list tool with no output schema, the description covers the essential gaps: pagination, resource semantics, filtering types, and the return-value coverage envelope. It does not explain how `all` interacts with `page`/`per_page` or the CSV format caveat, but the schema covers those.

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%, so every parameter is already documented in the schema, and the baseline is 3. The description adds minor interpretive value by explaining the STATIC/DYNAMIC distinction that the `type` filter operates on, but says nothing about `all`, `page`, `per_page`, `fields`, or `format`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List collections of the store') and adds scope detail by defining what a collection is (a curated set of product cards) and its two kinds, STATIC and DYNAMIC. It also names the related manage_collection_cards tool, which helps orient the agent, though it does not explicitly contrast itself with other list_* siblings.

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

Usage Guidelines3/5

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

Usage is only implied: the pairing with manage_collection_cards suggests this is the read side of card management, and 'paginated' hints at list-style consumption. There is no explicit statement of when to prefer this over a single-collection retrieval tool or any exclusion conditions.

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

Deploy Server

Other Tools