Skip to main content
Glama

ScraperAPI (Unofficial)

Scraperapi Amazon Search

scraperapi_amazon_search
Read-onlyIdempotent

Search Amazon and get structured results, product titles, ASINs, prices, ratings, thumbnails. Example: scraperapi_amazon_search({ query: "wireless earbuds", country: "us", tld: "com", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "wireless earbuds",
      "_apiKey": "your-scraperapi-api-key"
    },
    "name": "scraperapi_amazon_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldNoAmazon marketplace top-level domain, e.g. "com", "co.uk". Optional (default com).
queryYesSearch keywords, e.g. "wireless earbuds"
_apiKeyYesScraperAPI key
countryNoTwo-letter country code for proxy geotargeting, e.g. "us". Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds the concrete shape of the response (product titles, ASINs, prices, ratings, thumbnails), which matters because there is no output schema, but it says nothing about result count, pagination, credit consumption, or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler: the capability and its outputs come first, followed by a concrete example that doubles as a call template. The example string is long but carries information, so nothing is genuinely wasteful.

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

Completeness3/5

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

For a read-only search with fully documented parameters and rich annotations, the description covers purpose and return fields adequately. It stops short on operational details an agent would want in practice — how many results per call, how to page, and whether geotargeting or tld affects results.

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 four parameters including defaults for tld and country. The worked example still adds modest value by showing a realistic combination of query, country, tld and _apiKey in one call, reinforcing that only query and _apiKey are essential.

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?

States a specific verb and resource ("Search Amazon") and enumerates the returned fields (titles, ASINs, prices, ratings, thumbnails), so the agent knows exactly what it gets. It does not contrast itself with the sibling scraperapi_amazon_product (single-product lookup), which is the main ambiguity a router would face.

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

Usage Guidelines3/5

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

Usage is only implied through the sample invocation, which shows search-keyword querying with optional country/tld. There is no explicit statement of when to prefer this over scraperapi_amazon_product or scraperapi_google_search, and no exclusions or prerequisites beyond what the example demonstrates.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.