Apiguru Amazon Data

Feedback reviews for a seller

seller_reviews

Read-onlyIdempotent

Use for a seller's customer feedback (service, shipping). Not for product reviews (product_reviews). Returns paginated seller feedback, optionally filtered to a star-rating window. Price: $0.003 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: 'A' followed by 9-20 letters and digits, the seller= or me= value of a storefront URL (e.g. A2A1RNLLUK3HYA). 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.

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / geo / enum

Previous value: -[
-  "US",
-  "CA",
-  "DE",
-  "MX",
-  "UK",
-  "FR",
-  "IT",
-  "ES",
-  "AU",
-  "BR",
-  "IN",
-  "JP",
-  "NL",
-  "AE",
-  "PL",
-  "SA",
-  "SG",
-  "SE",
-  "TR",
-  "BE"
-]New value: +[
+  "US",
+  "CA",
+  "DE",
+  "MX",
+  "UK",
+  "FR",
+  "IT",
+  "ES",
+  "AU",
+  "BR",
+  "IN",
+  "JP",
+  "NL",
+  "AE",
+  "PL",
+  "SA",
+  "SG",
+  "SE",
+  "TR",
+  "BE",
+  "IE",
+  "ZA",
+  "EG"
+]

Changed2 schema fields changedSep 28, 2026

changedInput schema / properties / seller_id / description

Previous value: -"Amazon seller ID. Required."New value: +"Amazon seller id: 'A' followed by 9-20 letters and digits, the seller= or me= value of a storefront URL (e.g. A2A1RNLLUK3HYA). Required."

addedInput schema / properties / seller_id / pattern
```
Added value: +"^[Aa][A-Za-z0-9]{9,20}$"
```

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.9/5.0

Behavior5/5

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

Annotations only cover the read-only/idempotent safety profile; the description adds genuinely new behavior: per-call pricing ($0.003), a page cap of 100, 5 reviews per page, and the fact that Amazon exposes no total count so callers must paginate on has_next_page.

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?

Front-loads purpose and the exclusion, then packs pricing, filtering and pagination guidance into short declarative clauses with no 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?

An output schema exists so return values need no explanation, yet the description still supplies the pagination termination rule and the missing-total caveat, which are the things an agent actually needs to call this correctly in a loop.

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, but the description adds semantics the schema does not convey: from_rating/to_rating are jointly optional and omitting both yields unfiltered feedback, and how page interacts with has_next_page. Minor ambiguity remains between the description's '5 reviews a page' and the limit field's 'up to 48 rows' remark.

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 resource (a seller's customer feedback) plus the scope of what it covers (service, shipping) and explicitly names the sibling it is not for (product_reviews). An agent can distinguish it from product_reviews without inspecting either schema.

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?

Explicitly routes away from product_reviews and states the filtering rule ('omit both for unfiltered feedback') as well as the iteration rule ('page until has_next_page is false'). Both when-to-use and how-to-proceed are covered.

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.