Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

amazon_search

Search Amazon products by keyword, with optional sort order and page, to return ASIN, title, link, image, price, rating, reviews, sponsored and delivery flags in JSON.

Instructions

Search Amazon products. Searches amazon.com by keyword, with optional sort order and page. Each result card has the ASIN, title, link, image, price and list price, rating and review count, the bought-in-last-month figure, and flags for sponsored placement and free delivery.

Input Schema

NameRequiredDescriptionDefault
kYesSearch keyword
sNoSort order
pageNo1-based page number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the returned result-card fields (ASIN, title, link, price, rating, review count, bought-in-last-month, sponsored/free-delivery flags), which is genuinely useful for a tool with no output schema, but it omits result-count/page-size behavior, pagination limits, and whether sponsored placements are filtered out.

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, purpose front-loaded before the field inventory, with no filler. The long enumeration of card fields is justified because there is no output schema, though it could be trimmed slightly.

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 keyword-search tool with no annotations and no output schema, the description supplies the essential purpose and the shape of results. It is missing only secondary details like page size, result cap, and pagination behavior, which an agent would want for multi-page retrieval.

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 the schema already documents k, s and page. The description only restates that sort order and page are optional, adding no format, enum values, or ranking semantics beyond what the schema provides — baseline 3 applies.

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 opens with a specific verb+resource ('Search Amazon products') and scopes it to amazon.com by keyword with optional sort/page. It never names or contrasts a sibling (e.g. amazon_product, amazon_suggest), so the agent must infer that this is the keyword-search entry point rather than a detail or autocomplete tool.

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 implied by the name and description — use it when you have a keyword and want product listings — but there is no explicit when/when-not guidance or pointer to alternatives such as amazon_product for a known ASIN or amazon_suggest for query completion.

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