Skip to main content
Glama

Amazon search results

get_amazon_search_results
Read-only

Scrape Amazon search results using ScrapingBee.

Scope: one query per call. To run many queries in one pass, or to write results to disk instead of into the conversation, use the ScrapingBee CLI — scrapingbee <command> --input-file queries.txt --output-dir results.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "get_amazon_search_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoResponse-header label only.
pagesNoThe number of pages to scrape.
queryYesThe search query to perform.
domainNoThe Amazon domain to use for the search (e.g., com, co.uk, de).com
countryNoThe country code for localization (e.g., us, uk, de). Do not combine with a matching domain (e.g., country=fr&domain=fr).
sort_byNoThe sort order to use for the search (most_recent, price_low_to_high, price_high_to_low, featured, average_review, bestsellers).
add_htmlNoWhether to return the HTML along with the search results.
currencyNoThe currency code (ISO 4217) to display results (e.g., USD, GBP, EUR).
languageNoThe language code to display results (e.g., en, fr, de).
zip_codeNoThe ZIP code to use for delivery localization.
screenshotNoForce a browser screenshot (returns base64 image).
start_pageNoThe page number to start scraping from.
category_idNoThe category ID to use for the search.
merchant_idNoThe merchant ID to use for the search.
light_requestNoWhether to use a light request or not.
autoselect_variantNoAutomatically select the default/most-popular variant.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a non-mutating read, so the description only needs to add scoping context — which it does via the one-query-per-call limit and the note that results land in the conversation. It says nothing about credit cost, scraping failures/blocks, or pagination behavior across the `pages`/`start_page` parameters, leaving real operational gaps for a 16-parameter scraper.

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 short sentences, front-loaded with the purpose and the scope constraint, with the escape hatch to the CLI placed last. Nothing is repeated from the schema and no sentence is filler.

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?

An output schema exists, so return values need no explanation, and the schema fully documents all 16 parameters. What is missing is complexity-appropriate operational context for a scraping tool: credit consumption, rate/retry expectations, and how pages/start_page interact when scraping many pages.

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 every parameter including the non-obvious ones (domain vs country conflict, sort_by, autoselect_variant, light_request) is already documented in the schema. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema carries the load.

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 gives a specific verb and resource ("Scrape Amazon search results using ScrapingBee") and immediately bounds it with "Scope: one query per call." The Amazon-specific resource makes it distinguishable from get_google_search_results or get_walmart_search_results, though it never names a sibling tool explicitly.

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 states the operative constraint (one query per call) and names an alternative path (the ScrapingBee CLI with --input-file) for the multi-query or write-to-disk case. It does not address when to prefer get_amazon_product_details or get_amazon_pricing over a search, so coverage is clear but not exhaustive.

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.

Resources