Skip to main content
Glama
Sign In
A1 Yandex KIT MCP

A1 Yandex KIT MCP

by ztemerbekov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List variants

list_variants
Read-only

Lists sellable SKUs (variants) for catalog browsing or CSV export, with optional filters and pagination.

Instructions

Primary sellable catalog/export listing: list variants (SKUs), one item per sellable SKU. Use this for ordinary catalog or «выгрузи товары в CSV» requests; use list_products only for an explicit raw product-group export. Variants support optional filters and pagination. By default the API returns variants of all statuses except ARCHIVED. format:"csv" defaults to top-level scalar fields and serializes nested pricing/stocks as JSON cells; it does not create flat price or per-warehouse stock columns. List the archive with status ["ARCHIVED"]. If the response ever holds statuses outside the requested filter, the tool fails with STATUS_FILTER_IGNORED instead of returning the wrong catalog slice. For storefront page URLs use list_variant_links — it joins each item's relative_link_url with the store's b2c_url for you. 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.

Input Schema

NameRequiredDescriptionDefault
allNoFetch pages via auto-pagination, up to 500 items; inspect coverage and continue with explicit page reads if coverage is partial; ignores page/per_page.
nameNoCase-insensitive partial search by name, SKU, barcode or KIT ID.
pageNoPage number, starting at 1 (default 1).
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 variant status.
per_pageNoItems per page, 1-100 (default 25). Values outside the range are clamped.
product_idNoFilter by parent product ID (UUID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.2
    • changedInput schema / properties / all / description
      Previous value: -"Fetch all pages via auto-pagination, up to 500 items; ignores page/per_page."New value: +"Fetch pages via auto-pagination, up to 500 items; inspect coverage and continue with explicit page reads if coverage is partial; ignores page/per_page."
  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

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds substantial disclosure beyond that — default status exclusion of ARCHIVED, the STATUS_FILTER_IGNORED failure contract, the auto-pagination cap, and the coverage envelope with the rule that coverage:"partial" forbids claiming completeness. It also warns that format:"csv" serializes nested pricing/stocks as JSON cells rather than flattening them, a real behavioral trap.

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?

Front-loaded with the primary purpose and the sibling routing before edge cases, and every clause carries operative information. It is dense and somewhat run-on in the later sentences, but almost nothing is filler.

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?

There is no output schema, and the description compensates by describing the response shape: the coverage envelope fields (coverage, received, total_count, pages_read) and the CSV layout including the leading coverage comment line. For an 8-parameter list tool with no output schema, this is complete enough to call and report correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning beyond the schema by explaining what CSV output omits (no flat price or per-warehouse stock columns) and how the archive is reached via the status filter. It does not restate parameter formats that the schema already handles, which is appropriate.

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?

States a specific verb and resource ('list variants (SKUs), one item per sellable SKU') and immediately scopes it as the primary sellable catalog/export listing. It explicitly differentiates from list_products (raw product-group export) and list_variant_links (storefront URLs), so an agent can pick correctly without opening schemas.

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?

Gives explicit routing rules: use this for ordinary catalog or CSV export requests, use list_products only for an explicit raw product-group export, use list_variant_links for page URLs, and use status ["ARCHIVED"] for the archive. Alternatives and the conditions that select them are named directly.

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