Skip to main content
Glama
cdek-shopping-mcp

cdek-shopping-mcp

by heahoh

product_reviews

Retrieve customer reviews for a product, filter by media or written text, paginate results, and sort by date or rating.

Instructions

List customer reviews for a product.

Args:
    product_id: Product ID.
    has_media: If true, only reviews that include photos/video.
    has_text: If true, only reviews that include written text.
    page: Page number, 1-based.
    per_page: Reviews per page.
    sort_field: Field to sort by (e.g. date, rating).
    sort_order: Sort direction (asc/desc).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_id": "<product_id>"
    },
    "name": "product_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
has_textNo
per_pageNo
has_mediaNo
product_idYes
sort_fieldNo
sort_orderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and only implies read-only via the word 'List'. It says nothing about default page size, maximum per_page, total-count pagination metadata, sort defaults, or whether reviews include ratings, authors, and timestamps in the response.

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?

The one-line summary is front-loaded and the per-argument list is easy to scan, with no rambling prose. Minor waste in tautological entries such as 'product_id: Product ID' and 'per_page: Reviews per page', which restate the parameter names.

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

Completeness2/5

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

For a 7-parameter tool with zero schema description coverage, no annotations, and no output schema, the description is too thin. It never describes the review shape returned, pagination limits, or ordering defaults, leaving an agent unable to predict what it will get back or how to page reliably.

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 coverage is 0%, so the description must compensate, and it does partially: it clarifies that page is 1-based, explains the has_media/has_text filters, and gives examples for sort_field (date, rating) and sort_order (asc/desc). However, product_id is defined only as 'Product ID', and it omits the null defaults, the accepted sort_field value set, and any per_page bounds.

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 opens with a specific verb and resource, 'List customer reviews for a product', which tells an agent exactly what data comes back and the scope (per-product). No sibling tool in the catalog covers reviews, so the purpose is unambiguous even without explicit differentiation.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as whether the product must exist, and no routing to alternatives (get_product, get_product_summary) when aggregate rating data is wanted instead of individual reviews. Usage is only inferable from the purpose sentence.

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