Apiguru Amazon Data

Feedback reviews for a seller

seller_reviews

Read-onlyIdempotent

Returns paginated seller feedback, optionally filtered to a star-rating window. Price: $0.01 per call. from_rating and to_rating are optional; omit both for unfiltered feedback. A page holds 5 reviews and the answer carries current_page and has_next_page; Amazon exposes no total, so page until has_next_page is false (up to page 100).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`geo`	No	Marketplace country code.	US
`page`	No	Result page, 1-based, 5 reviews a page; has_next_page in the answer says whether another exists.
`limit`	No	How many seller reviews to return from this page (0 = all of them). A full page is up to 48 rows and about 54 KB, which most clients spill to a file instead of showing inline. The answer carries _truncated with the true count when it trims.
`fields`	No	Comma-separated row fields to return instead of the light set, e.g. "asin,product_title,product_price". Rows list what they left out under _omitted_fields.
`compact`	No	Return light rows: identity, price, rating, badges and one delivery_date, dropping the long delivery prose that repeats itself across three fields. false returns every field the REST API sends (roughly 3x the size).
`seller_id`	Yes	Amazon seller ID. Required.
`to_rating`	No	Highest star rating to include, 1-5.
`from_rating`	No	Lowest star rating to include, 1-5.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`success`	No
`request_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 8, 2026

changedInput schema / properties / from_rating / description

Previous value: -"Lower bound of the star-rating filter."New value: +"Lowest star rating to include, 1-5."

changedInput schema / properties / page / description

Previous value: -"Result page, 1-based."New value: +"Result page, 1-based, 5 reviews a page; has_next_page in the answer says whether another exists."

changedInput schema / properties / to_rating / description

Previous value: -"Upper bound of the star-rating filter."New value: +"Highest star rating to include, 1-5."

First observedSep 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: the $0.01 per-call cost, the 5-review page size, the lack of a total count, and the page-100 cap. This gives an agent important operational expectations.

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?

The description is compact: three sentences, each earning its place. It front-loads the core purpose, then adds cost, filtering, and pagination guidance. No filler or redundant restating of the tool name.

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?

With a rich input schema, output schema, and strong annotations, the description covers the essential operational details well. The only gap is the unresolved contradiction between the stated page size and the `limit` parameter's description, which prevents it from being fully complete for an autonomous agent.

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 description coverage is 100%, so the baseline is 3. The description adds meaning by explaining that from_rating/to_rating are optional and omitting both yields unfiltered feedback, and by clarifying pagination behavior. However, it does not reconcile the internal inconsistency between the '5 reviews a page' statement and the `limit` parameter's 'full page is up to 48 rows' description, so it could confuse agents about page size and limit semantics.

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 opens with a specific verb and resource: 'Returns paginated seller feedback'. It also clarifies the optional star-rating window, immediately distinguishing it from sibling tools like product_reviews. This is unambiguous and names exactly what the tool does.

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?

It gives concrete instructions: omit both rating parameters for unfiltered feedback, and page until has_next_page is false (up to page 100). It does not explicitly name sibling alternatives or state when not to use this tool, so it falls just short of a 5.

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

All Apiguru Amazon Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.