Retrieve normalized Amazon product details by ASIN, including pricing, availability, overview, review samples, and descriptions.
Retrieve Amazon product details. Returns normalized product details for an Amazon ASIN on amazon.com, including pricing, availability, overview data, inline review samples, and descriptive content.
| Name | Required | Description | Default |
|---|---|---|---|
| asin | Yes | Amazon ASIN | |
| currency | No | Amazon currency | |
| language | No | Amazon language |
Changes observed during successful MCP inspections.
v1.17.5Input schema / properties / currency / enumAdded value: +[
+ "USD"
+]Input schema / properties / language / enumAdded value: +[
+ "en_US"
+]v1.6.0v1.6.0v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden. It clearly says 'Returns normalized product details' indicating a read operation, and enumerates the data categories (pricing, availability, overview, inline review samples, descriptive content), giving the agent a good sense of what to expect. It doesn't mention rate limits or pagination, but for a single-item retrieval, this is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One well-structured sentence lists the purpose and the key data elements without excessive verbosity. It front-loads the action verb and resource, followed by the data scope. No fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is complete enough for a retrieval tool with only one required parameter. It notes the marketplace (`amazon.com`) and the scope of data returned. Since there's no output schema, this is helpful for setting expectations. Missing details like authentication or rate limits are not critical for a single-item lookup.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 100% coverage, with descriptions for each parameter, so the description adds little beyond that. It reinforces that the main identifier is `asin`, but does not add extra context like acceptable formats for ASINs or how currency/language defaults work. Baseline 3 is appropriate given the high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it retrieves Amazon product details for a specific ASIN, including pricing, availability, and review samples. It distinguishes itself from sibling tools that are mostly news/article tools or other product pages for different retailers (e.g., modaoperandi_product, vestiaire_product). However, it doesn't explicitly contrast with amazon_search or amazon_suggest, which are also amazon-related, but those names imply search vs. detail retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when you have an ASIN and need product details, but it doesn't explicitly state when not to use it or mention alternatives like amazon_search for finding products by query. It also doesn't mention prerequisites like having an ASIN already from a search step.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.