Skip to main content
Glama
Sign In
A1 Yandex KIT MCP

A1 Yandex KIT MCP

by ztemerbekov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List orders

list_orders
Read-only

Lists store orders with pagination and newest-first sorting, enabling CRM lookup and incremental sync via updated_from/updated_to filters; check coverage to avoid claiming partial listings are complete.

Instructions

List orders of the store (paginated), newest first by default. Each order carries customer_id (look the buyer up with get_customer) and items[].name, so a CRM can link an order to its customer card without extra calls. updated_from/updated_to filter by last-change time, which is what an incremental sync should poll on: an order that only changed status still falls inside the window, while a created-at filter would miss it. Sync recipe: updated_from=, sort_by=updated_at, sort_direction=asc, then advance the cursor to the largest updated_at seen — an order that changes mid-paging moves to the end instead of being skipped, and an all=true run cut off at 500 items resumes from that cursor. The filter is inclusive on both ends, so the boundary order comes back on the next poll — deduplicate by order ID. 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 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.
redactNoUse redact:true when the task does not need personal data (e.g. counting or aggregating orders) — personal fields (name, phone, email, date of birth, delivery address and its parts, notes) are replaced with "[redacted]". Applies to the response only; request bodies are never redacted. Default false.
sort_byNoSort field (default "created_at"). Use "updated_at" for incremental sync.
per_pageNoItems per page, 1-100 (default 25). Values outside the range are clamped.
updated_toNoLatest order update time, inclusive. RFC 3339 date-time, e.g. "2026-10-02T00:00:00Z".
updated_fromNoEarliest order update time, inclusive. RFC 3339 date-time, e.g. "2026-10-01T00:00:00Z".
sort_directionNoSort direction (default "desc"). Use "asc" with sort_by "updated_at" for sync.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.11.0
    • addedInput schema / properties / sort_by
      Added value: +{
+  "description": "Sort field (default \"created_at\"). Use \"updated_at\" for incremental sync.",
+  "enum": [
+    "created_at",
+    "updated_at"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / sort_direction
      Added value: +{
+  "description": "Sort direction (default \"desc\"). Use \"asc\" with sort_by \"updated_at\" for sync.",
+  "enum": [
+    "asc",
+    "desc"
+  ],
+  "type": "string"
+}
  2. Changed3 schema fields changedv1.8.0
    • changedInput schema / properties / redact / description
      Previous value: -"Use redact:true when the task does not need personal data (e.g. counting or aggregating orders) — personal fields (name, phone, email, delivery address and its parts, notes) are replaced with \"[redacted]\". Applies to the response only; request bodies are never redacted. Default false."New value: +"Use redact:true when the task does not need personal data (e.g. counting or aggregating orders) — personal fields (name, phone, email, date of birth, delivery address and its parts, notes) are replaced with \"[redacted]\". Applies to the response only; request bodies are never redacted. Default false."
    • addedInput schema / properties / updated_from
      Added value: +{
+  "description": "Earliest order update time, inclusive. RFC 3339 date-time, e.g. \"2026-10-01T00:00:00Z\".",
+  "type": "string"
+}
    • addedInput schema / properties / updated_to
      Added value: +{
+  "description": "Latest order update time, inclusive. RFC 3339 date-time, e.g. \"2026-10-02T00:00:00Z\".",
+  "type": "string"
+}
  3. Changed3 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"
+}
    • addedInput schema / properties / redact
      Added value: +{
+  "description": "Use redact:true when the task does not need personal data (e.g. counting or aggregating orders) — personal fields (name, phone, email, delivery address and its parts, notes) are replaced with \"[redacted]\". Applies to the response only; request bodies are never redacted. Default false.",
+  "type": "boolean"
+}
  4. First observedv1.3.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses pagination defaults, inclusive update-time filtering, mid-paging behavior, the 500-item all=true cutoff and resume strategy, deduplication needs at boundaries, and the machine-readable coverage envelope. It also includes a strong operational warning that coverage:"partial" must be reflected in the user-facing answer.

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?

Although longer than a simple list tool, every part is front-loaded and serves the complexity of this operation: purpose first, then output linkage, sync behavior, filtering boundaries, and coverage semantics. The density is appropriate for a 10-parameter sync-capable listing tool.

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?

With no output schema, the description carries responsibility for explaining response shape and does so via customer_id, items[].name, and the coverage envelope. It also supplies the sync recipe and edge-case behavior needed to call the tool correctly in incremental and paginated workflows.

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 already 100%, so the baseline is 3. The description adds meaningful cross-parameter semantics: updated_from/updated_to are last-change filters for incremental sync, and sort_by=updated_at with sort_direction=asc is the correct sync combination, while all=true has a 500-item cutoff with cursor resumption.

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?

The description clearly states a specific verb and resource: "List orders of the store", with pagination and default ordering. It does not explicitly distinguish this from relevant list siblings such as get_customer_orders, so an agent gets a clear purpose but no direct sibling routing.

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 strong usage context for incremental sync, including an explicit recipe with updated_from, sort_by=updated_at, and sort_direction=asc. It does not state when to prefer get_order or get_customer_orders instead, so guidance is clear but lacks sibling exclusions.

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