Easyparser — Amazon Product & Seller Data

get_product_detail

Read-only

Fetch complete, structured information about a single Amazon product: title, brand, images, feature bullets, description, Buy Box price and availability, Prime eligibility, rating and review count, Best Sellers Rank, category path, variants, specifications, and top reviews. This is the primary tool for product analysis, listing enrichment, and price monitoring.

Use this tool when you need a full product profile. If you only need competing seller prices, use get_product_offers instead (cheaper context). If you only need the sales rank, use get_bestseller_rank. If you only need shipping dimensions or the FBA fee category, use get_package_dimensions.

Provide EITHER the identifier field OR url — never both. Costs 1 credit; set a_plus_content to true only when the user explicitly asks about enhanced brand content, as it costs 1 extra credit.

Input Schema

Name	Required	Description	Default
`url`	No	Full Amazon product URL (e.g. https://www.amazon.com/dp/B0CJB6V2L5). Use this when the user pastes a link instead of an ASIN.
`asin`	No	Amazon Standard Identification Number — a 10-character alphanumeric product identifier (e.g. B0CJB6V2L5). Found in the product URL after /dp/ or /gp/product/.
`domain`	No	Amazon marketplace domain extension. Determines the regional Amazon site the data is fetched from. Use the domain that matches the user's market — prices, availability and rankings differ across marketplaces.	.com
`currency`	No	ISO currency code for price display (e.g. usd, eur, try). Prices are converted by Amazon's own display logic.
`language`	No	Language code for the Amazon page, in locale format (e.g. en_US, de_DE, tr_TR). Affects the language of titles, descriptions and reviews in the response.
`seller_id`	No	Fetch the product as offered by a specific seller (their Seller ID). Only use when the user asks about a specific merchant's offer.
`a_plus_content`	No	Set true to include the 'From the manufacturer' A+ enhanced brand content. Costs 1 additional credit. Default false.

Output Schema

Name	Required	Description
`data`	No	Parsed Amazon data for the operation.
`success`	Yes	True when the request completed.
`operation`	Yes	Easyparser operation that ran, e.g. DETAIL or OFFER.
`request_id`	No	Easyparser request ID, useful for support and error logs.
`credits_used`	No	Credits charged for this request.
`credits_remaining`	No	Credits left on the account after this request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "credits_remaining": {
+      "description": "Credits left on the account after this request.",
+      "type": "number"
+    },
+    "credits_used": {
+      "description": "Credits charged for this request.",
+      "type": "number"
+    },
+    "data": {
+      "description": "Parsed Amazon data for the operation."
+    },
+    "operation": {
+      "description": "Easyparser operation that ran, e.g. DETAIL or OFFER.",
+      "type": "string"
+    },
+    "request_id": {
+      "description": "Easyparser request ID, useful for support and error logs.",
+      "type": "string"
+    },
+    "success": {
+      "description": "True when the request completed.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "operation"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare readOnly/openWorld/non-destructive, and the description adds economics the structured data does not contain: 1 credit per call, +1 credit for a_plus_content, and the hard constraint that exactly one of identifier or url must be supplied. That credit cost and the mutual-exclusion rule are the practical behavioral facts an agent needs before calling.

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-loaded with the payoff ('Fetch complete, structured information about a single Amazon product'), then routing, then constraints and costs. The long field enumeration is dense but information-bearing, and the alternative-routing sentences are one clause each 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, and the surrounding gaps are covered: sibling disambiguation, identifier mutual exclusivity, credit cost, and the opt-in cost of a_plus_content. Nothing an agent needs in order to call this correctly is missing.

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 parameter docs already carry the semantics; the baseline is 3. The description goes beyond it by stating the either/or exclusivity between asin and url and by giving a negative condition for a_plus_content, which is decision guidance the schema does not contain.

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?

Names a specific verb (Fetch) and resource (single Amazon product) and enumerates the returned payload — title, brand, Buy Box price, BSR, variants, etc. It also explicitly distinguishes itself from get_product_offers, get_bestseller_rank, and get_package_dimensions, so an agent can route 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?

The second and third paragraphs are pure routing guidance: 'use this when you need a full product profile' plus three named alternatives each with the narrower condition that selects them ('only need competing seller prices', 'only need sales rank', 'only need shipping dimensions or FBA fee category'). It also states when to enable a_plus_content ('only when the user explicitly asks').

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

All Easyparser — Amazon Product & Seller 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.