Skip to main content
Glama
ztemerbekov

A1 Yandex KIT MCP

by ztemerbekov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List videos

list_videos
Read-only

Retrieve product videos from a Yandex KIT store with pagination, status filters, and CSV export. If coverage is partial, the response flags it, so the answer won't claim the listing is complete.

Instructions

List product videos of the store (paginated), oldest upload first. The API requires a status filter; defaults to all four statuses when not provided. 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

TableJSON Schema
NameRequiredDescriptionDefault
allNoFetch all pages via auto-pagination, up to 500 items; ignores page/per_page.
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 processing status (default: all of UPLOADED, PROCESSING, READY, ERROR).
per_pageNoItems per page, 1-100 (default 25). Values outside the range are clamped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv1.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Even with readOnlyHint=true, the description adds meaningful behavioral detail: pagination order, the status-filter requirement/defaults, and the critical coverage-envelope semantics. The explicit warning that coverage:'partial' must be reflected and forbids claiming completeness is valuable beyond what annotations provide.

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?

Three sentences, each earning its place: purpose and ordering first, then status-filter behavior, then the coverage-envelope requirement. The most important operational nuance is front-loaded and clearly stated without fluff.

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?

For a paginated read-only list tool, the description is complete: it specifies scope, ordering, pagination, status defaults, and the critical coverage-handling rule. The input schema fully covers parameters, and no output schema exists, but the description provides the key response-related behavior an agent needs for correct invocation and interpretation.

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 the parameter schema already documents all six parameters in detail. The description adds some useful context around the status filter and coverage semantics, but it does not substantially extend parameter-level meaning beyond the schema.

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 uses a specific verb and resource: 'List product videos of the store (paginated), oldest upload first.' It clearly distinguishes itself from sibling tools like get_video (single video) and upload_video (write operation) by communicating that this is a paginated listing read.

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 on how the listing behaves: pagination order, status filtering, and auto-pagination behavior via 'all' are implied through the schema. It does not explicitly name alternatives like get_video for single-video retrieval, so it stops short of full when-to-use vs when-not-to-use guidance.

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