ecommerce.amazon.search
Search Amazon products by keyword — filter by price range, sort by relevance/price/rating/reviews/newest. Returns title, ASIN, price, rating, Prime flag, image. 12 marketplaces: US, UK, CA, DE, FR, IT, ES, AU, IN, MX, BR, JP (Canopy API)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ecommerce.amazon.search.md
What ecommerce.amazon.search does on Apibase
AI agents call ecommerce.amazon.search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Page number for pagination |
sort | string | — | Sort order: relevance, price_asc, price_desc, rating, reviews, newest |
query | string | Yes | Search keywords (e.g. "wireless headphones", "raspberry pi 5") |
domain | string | — | Amazon marketplace: US, UK, CA, DE, FR, IT, ES, AU, IN, MX, BR, JP (default US) |
price_max | number | — | Maximum price filter (in marketplace currency) |
price_min | number | — | Minimum price filter (in marketplace currency) |
Parameters from the server's own tool schema.
Why ecommerce.amazon.search is rated Low
Queries product data with no side effects or state modification; pure retrieval operation.
From the tool's definition Search Amazon products by keyword — filter, sort, returns title, ASIN, price, rating.
Attacks that exploit this kind of access
The rule that runs ecommerce.amazon.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ecommerce.amazon.search, this is the rule to start with:
ecommerce.amazon.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every ecommerce.amazon.search call is checked against it from then on.
Questions about ecommerce.amazon.search
Search Amazon products by keyword — filter by price range, sort by relevance/price/rating/reviews/newest. Returns title, ASIN, price, rating, Prime flag, image. 12 marketplaces: US, UK, CA, DE, FR, IT, ES, AU, IN, MX, BR, JP (Canopy API). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ecommerce.amazon.search accepts 6 parameters: page, sort, query, domain, price_max, price_min. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for ecommerce.amazon.search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Apibase. Nothing to install.
ecommerce.amazon.search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ecommerce.amazon.search rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for ecommerce.amazon.search. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
ecommerce.amazon.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue