Apiguru Amazon Data

Product detail for up to 20 ASINs in one call

product_details_batch

Read-onlyIdempotent

Use to enrich a list of ASINs in one call; compare the ASINs in results with the ones you sent. Batch variant of product_details. Accepts a comma-separated ASIN list, deduplicates it, and fetches all of them concurrently. Far cheaper and faster than N single calls. Price: $0.0024 per item (max 20). Billed per ASIN processed, including ones that come back not-found. More than 20 ASINs returns 413. Bullet points and specs are what Amazon shows for the listing; on multi-variant listings they can describe the product family rather than the exact variant. A null field means Amazon did not show it. ASINs Amazon has no record for on that marketplace are listed in not_returned (billed, like a not-found product_details call; retrying will not help). The batch record comes from Amazon's app, not the product page: price, rating, availability, images, bullets and variants, but no best-seller ranks, no category path and no merchant (seller) id. For those call product_details per ASIN. On an API key both cost one request per ASIN, so the batch saves calls and time, not money; keyless (x402) it is also cheaper per item.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`geo`	No	Marketplace country code.	US
`asins`	Yes	Comma-separated ASIN list, maximum 20 after de-duplication. Each must be 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.
`fields`	No	Comma-separated top-level fields to return instead of the compact set, e.g. "tech_specs,product_information". Any response lists what it left out under _omitted_fields.
`compact`	No	Return the compact record (about 4 KB: identity, price, rating, availability, bullets, category, offer, buy box). false returns the full record (about 75 KB, includes from_manufacturer, tech_specs, product_information, product_reviews).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	No
`request_id`	No
`country_code`	No
`response_time`	No
`amazon_request_count`	No
`billable_requests_count`	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 30, 2026

changedInput schema / properties / asins / description

Previous value: -"Comma-separated ASIN list, maximum 20 after de-duplication. Each must be 10 uppercase alphanumeric characters."New value: +"Comma-separated ASIN list, maximum 20 after de-duplication. Each must be 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."

removedInput schema / properties / asins / pattern

Removed value: -"^[A-Z0-9]{10}(,[A-Z0-9]{10})*$"

Changed1 schema field changedSep 6, 2026
- addedInput schema / properties / asins / pattern
```
Added value: +"^[A-Z0-9]{10}(,[A-Z0-9]{10})*$"
```
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 cover safety (readOnly, idempotent, non-destructive), and the description adds substantial context they cannot: per-item pricing and billing on not-found ASINs, the 20-item/413 limit, dedup and concurrency behavior, and data provenance (app-sourced record lacking best-seller ranks, category path, merchant id). It also explains null semantics and that not_returned items are billed and unretryable, which is exactly the kind of behavior an agent needs before invoking.

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 most important information (purpose, batch advantage, limits, cost) is front-loaded, and nearly every sentence adds operational value. There is mild redundancy: the not-returned/billing point is restated once in the results sentence and again in the not_returned sentence, which could be consolidated.

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 an output schema present, the description need not explain return shape, yet it still covers edge cases an agent must anticipate: 413 on >20 ASINs, billed not-found results, multi-variant listing caveats, and provenance gaps. Nothing needed to invoke or interpret a batch call is missing.

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 100%, so all four parameters (geo, asins, fields, compact) are already documented, including URL handling and de-dup rules. The description reinforces dedup and ASIN-list handling but adds little beyond the schema, and never mentions the compact/fields toggles, so baseline 3 applies.

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 names a specific verb and resource ('enrich a list of ASINs in one call') and explicitly positions itself as the 'batch variant of product_details', so it is instantly distinguishable from its sibling. The title and first sentence together pin down scope (up to 20 ASINs) and the core action.

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?

It states when to use it versus the alternative ('Far cheaper and faster than N single calls'; 'For those call product_details per ASIN') and even qualifies the economics by auth mode ('On an API key both cost one request per ASIN... keyless (x402) it is also cheaper per item'). The guidance is unusually explicit about the tradeoff conditions.

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.