apiguru-amazon-data

Customer reviews for a single ASIN

product_reviews

Read-onlyIdempotent

Get customer ratings, Amazon's AI summary, rating histogram, and page reviews for one product, filterable by star rating and marketplace.

Instructions

Use for what customers say about one product. Not for its full review history (Amazon serves full and star-filtered review lists only to signed-in accounts) or for seller feedback (seller_reviews). Returns the overall rating, rating count, review_histogram (percent of all ratings per star), Amazon's 'customers say' AI summary where that marketplace shows one, and the reviews on the product page (typically up to 8 from this marketplace and 5 from other countries), each with rating, review_date, review_country, from_this_marketplace, verified flag and helpful_votes; from_rating/to_rating keep a star window. Price: $0.003 per call. Same 404-billed / 503-not-billed semantics as product_details. No paging or sort: the reviews are those on the product page; review_coverage says how many and from where. from_rating/to_rating filter them. review_histogram (here and on product_details) gives the share of every rating. customers_say is null where Amazon shows no summary (several marketplaces never do); customers_say_note then says so.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`geo`	No	Marketplace country code.	US
`asin`	Yes	Single Amazon ASIN, 10 uppercase alphanumeric characters. An Amazon product URL (…/dp/ASIN) works too, in place of an ASIN; lower case is fine. A URL's domain sets the marketplace unless geo says otherwise.
`to_rating`	No	Highest star rating to include, 1-5. from_rating=1&to_rating=3 keeps the critical ones among them.
`from_rating`	No	Lowest star rating to include, 1-5. Filters the reviews the product page shows (see review_coverage).
`max_reviews`	No	Cap on individual reviews returned (0 = all). The rating summary, review_histogram and customers_say are always returned; _reviews_total is the number of reviews on the product page (not all reviews; see review_coverage).

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.1.50Oct 4, 2026

changedInput schema / properties / asin / description

Previous value: -"Single Amazon ASIN, 10 uppercase alphanumeric characters."New value: +"Single Amazon ASIN, 10 uppercase alphanumeric characters. An Amazon product URL (…/dp/ASIN) works too, in place of an ASIN; lower case is fine. A URL's domain sets the marketplace unless geo says otherwise."

changedInput schema / properties / asin / pattern

Previous value: -"^[A-Z0-9]{10}$"New value: +"^\\s*(?:[A-Za-z0-9]{10}|https?://\\S+)\\s*$"

addedInput schema / properties / from_rating

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 5,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Lowest star rating to include, 1-5. Filters the reviews the product page shows (see review_coverage).",
+  "title": "From Rating"
+}

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"
+]

changedInput schema / properties / max_reviews / description

Previous value: -"Cap on individual reviews returned (0 = all). The rating summary and customers_say are always returned; _reviews_total says how many exist."New value: +"Cap on individual reviews returned (0 = all). The rating summary, review_histogram and customers_say are always returned; _reviews_total is the number of reviews on the product page (not all reviews; see review_coverage)."

addedInput schema / properties / to_rating

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 5,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Highest star rating to include, 1-5. from_rating=1&to_rating=3 keeps the critical ones among them.",
+  "title": "To Rating"
+}

First observedv0.1.0Sep 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations cover read-only/idempotent safety, but the description adds substantial behavior beyond them: per-call pricing ($0.003), 404-billed vs 503-not-billed semantics, absence of paging/sorting, and the null behavior of customers_say with the customers_say_note fallback. These are exactly the operational facts an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the use statement and exclusions, which is good, but the body is a dense run-on paragraph that repeats itself (review_histogram and from_rating/to_rating are each explained twice, review_coverage referenced multiple times). It is informative but not tight.

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?

Despite an output schema existing, the description usefully characterizes the return shape (rating, histogram, customers_say, per-review fields and coverage limits) and the filtering semantics, leaving nothing material for an agent to guess when deciding whether and how to call it.

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 real meaning: from_rating/to_rating define a star window over the product-page reviews, max_reviews=0 means all while summary fields are always returned, and a URL in the asin slot can set the marketplace. That is genuine value over the schema text.

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?

Opens with a specific use statement ('what customers say about one product') tied to a single ASIN, and explicitly differentiates from siblings: seller feedback -> seller_reviews, full review history -> not available. An agent can route correctly without opening any 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?

Gives both when-to-use and when-not-to-use, naming seller_reviews as the alternative and explaining why full/star-filtered review histories are unavailable (signed-in-only). It also clarifies the relationship to product_details (shared review_histogram) and the no-paging/no-sort constraint.

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

Deploy Server