Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Get products from Amazon (14 marketplaces)

get_amazon_products
Read-onlyIdempotent

Amazon products from search words or links on 14 marketplaces (US, UK, DE, FR, IT, ES, CA, IN, JP, AU, MX, BR, NL, AE): title, ASIN, price, list price, rating, ratings count, bought last month and sponsored flag.

Instructions

Amazon products from search words or links on 14 marketplaces (US, UK, DE, FR, IT, ES, CA, IN, JP, AU, MX, BR, NL, AE): title, ASIN, price, list price, rating, ratings count, bought last month and sponsored flag. With details on: brand, features, specs, images, best sellers rank and seller. Filter by rating and price. Useful for price checks, product research and competitor tracking. Runs the Apify Actor tacps126/amazon-products on your Apify account (about $0.001 per search result, or $0.0025 per product with full details; spend per call is capped at $0.5).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_amazon_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksNoAmazon product or search links, or ASINs.
queriesNoSearch words as typed on Amazon, e.g. ["wireless earbuds"].
max_itemsNoMaximum results to return (default 50, max 1000). Cost scales with this.
max_priceNoHighest price to keep, in the marketplace currency.
min_ratingNoLowest star rating to keep, e.g. 4.
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
marketplaceNoAmazon country site for searches.us
skip_sponsoredNoDrop sponsored (ad) placements.
include_detailsNoOpen each product page for brand, features, specs and seller (extra cost per product).
pages_per_searchNoResult pages to read per search.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this a read-only, open-world, idempotent, non-destructive operation, so the bar is lower. The description still adds real behavioral value the annotations cannot: per-result and per-detail pricing, a $0.5 per-call spend cap, that the Actor runs on the caller's Apify account, and that include_details incurs extra cost per product. The only gap is the absence of rate-limit or latency expectations.

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?

Purpose and scope are front-loaded in the first clause, followed by returned fields, use cases, and cost last. There is no filler, and pricing is deferred to the end where it belongs for a decision-support note.

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?

With 10 parameters, an output schema, and full annotations, the description covers the areas structured data cannot: cost model, spend cap, marketplace breadth, and filtering intent. The remaining minor gap is guidance on how the search-volume controls (max_items, pages_per_search) trade off against the stated spend cap.

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 baseline would be 3; the description earns above that by expanding what 'details' actually contains (brand, features, specs, images, best sellers rank and seller) beyond the schema's shorter list, and by framing filters as 'filter by rating and price'. It still does not clarify interactions such as how max_items and pages_per_search jointly affect volume or cost.

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 and resource ('Amazon products from search words or links on 14 marketplaces'), enumerates the marketplaces, and lists exactly which fields come back (title, ASIN, price, rating, bought last month, sponsored flag). This is enough to separate it from sibling retail tools like get_shopify_products or get_walmart_products without opening a schema.

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 concrete use cases ('price checks, product research and competitor tracking') and explains the two input modes (search words vs links/ASINs), which clarifies when each parameter applies. It stops short of naming an alternative tool or an explicit when-not-to-use condition, so it is strong context rather than full routing guidance.

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