Skip to main content
Glama
easyparser-com

Easyparser

Official

get_product_detail

Read-only

Retrieve complete structured data for any Amazon product, including title, brand, price, ratings, and reviews. Ideal for product analysis, listing enrichment, and price monitoring.

Instructions

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

TableJSON Schema
NameRequiredDescriptionDefault
urlNoFull Amazon product URL (e.g. https://www.amazon.com/dp/B0CJB6V2L5). Use this when the user pastes a link instead of an ASIN.
asinNoAmazon Standard Identification Number — a 10-character alphanumeric product identifier (e.g. B0CJB6V2L5). Found in the product URL after /dp/ or /gp/product/.
domainNoAmazon 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
currencyNoISO currency code for price display (e.g. usd, eur, try). Prices are converted by Amazon's own display logic.
languageNoLanguage 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_idNoFetch 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_contentNoSet true to include the 'From the manufacturer' A+ enhanced brand content. Costs 1 additional credit. Default false.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.4.0

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/destructive annotations, the description discloses credit costs, the extra cost of a_plus_content, and the constraint to provide either an identifier or a URL but never both. It could add more about rate limits or response shape, but the annotations already cover the safety profile and the added operational details are valuable.

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?

The description is tightly structured: purpose and data scope first, routing guidance second, then operational constraints. Every sentence adds useful selection or invocation information, with no filler or repetition of schema details.

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?

For a complex 7-parameter tool with no output schema, the description provides a full picture: what data comes back, which sibling covers narrower needs, how to choose identifier vs URL, cost implications, and the a_plus_content special case. The schema covers parameter semantics, so nothing essential 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 coverage is 100%, so the schema already documents all parameters. The description adds extra semantic value by explaining the mutually-exclusive identifier/URL rule, the credit cost tied to a_plus_content, and the default behavior, which goes beyond what the schema states.

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 opens with a specific verb ('Fetch complete, structured information') and names the resource ('single Amazon product') plus an explicit list of returned fields. It distinguishes this tool from siblings like get_product_offers and get_bestseller_rank by emphasizing the full-product-profile scope.

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 'Use this tool when you need a full product profile' and then explicitly routes narrower needs to alternative tools: get_product_offers for seller prices, get_bestseller_rank for rank only, and get_package_dimensions for shipping dimensions/FBA category. This gives an agent crisp selection rules.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/easyparser-com/mcp-easyparser'

If you have feedback or need assistance with the MCP directory API, please join our Discord server