Skip to main content
Glama
Sign In
Decodo

Decodo MCP Server

by Decodo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Amazon Product

amazon_product
Read-only

Fetch an Amazon product page by ASIN and return parsed JSON details such as title, price, rating, and description.

Instructions

Fetch an Amazon product page by ASIN through the Decodo Web Scraping API (amazon_product target) and return its details parsed as JSON. Use it when you know the product's ASIN and need its title, price, rating or description. Docs: https://help.decodo.com/docs/web-scraping-api-amazon-product

Input Schema

NameRequiredDescriptionDefault
geoNoAmazon geo location (e.g., 10001 for US ZIP code)
queryYesAmazon product ASIN (e.g., "B09H74FXNW")
domainNoAmazon domain (e.g., amazon.com, amazon.co.uk)
jsRenderNoShould the request be opened in a headless browser, false by default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • removedInput schema / properties / deviceType
      Removed value: -{
-  "description": "Device type to emulate for the request",
-  "enum": [
-    "desktop",
-    "mobile",
-    "tablet"
-  ],
-  "type": "string"
-}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, covering the safety profile. The description adds that the result is parsed JSON and identifies the Decodo API target, but it does not disclose rate limits, failure modes, auth needs, or how geo/domain/jsRender affect behavior.

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?

Two tight sentences front-load the purpose and usage condition, followed by a documentation link. There is no wasted or redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter tool with full schema coverage and annotations, the description covers purpose, usage condition, API target, and return format. Since there is no output schema, it could say more about the returned JSON shape, but it does list representative fields.

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 description coverage is 100%, so parameter meaning is primarily carried by the schema. The description reinforces that query is the product ASIN, but it does not add meaning for geo, domain, or jsRender beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: fetch an Amazon product page by ASIN and return parsed JSON details. It implies the ASIN-based use case, which helps distinguish it from search-oriented siblings, but it does not explicitly name those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage condition: use when you know the product's ASIN and need title, price, rating or description. It does not explicitly state when not to use it or name sibling alternatives like amazon_search.

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

Deploy Server

Other Tools