Crawlora MCP

zappos_search

Read-only

Search Zappos's product catalog by keyword, with real page-based pagination: normalized products with brand, pricing, sale status, rating, and review count, plus filterable facets (gender, department, shoe size, and more) each with a live result count and its own drill-down URL. Requesting a page beyond the available results returns a normal, empty result rather than an error.

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": {
      "term": "<term>"
    },
    "name": "zappos_search"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Result page, 1-based, defaults to 1
`term`	Yes	Search keyword

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026
- addedInput schema / properties / page / description
```
Added value: +"Result page, 1-based, defaults to 1"
```
- addedInput schema / properties / term / description
```
Added value: +"Search keyword"
```
First observedOct 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful non-obvious behavior: page-based pagination and that an out-of-range page returns an empty result rather than an error, which tells the agent how to terminate iteration. No auth or rate-limit context, hence not a 5.

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?

Front-loaded with the core action, and every clause carries information (output shape, facets, page behavior). It is a single dense sentence with mild output-list redundancy, but nothing is wasted.

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?

Given an output schema exists, the description needn't detail returns, yet it summarizes them and adds the pagination termination rule. Combined with readOnly/openWorld annotations, an agent has enough to call it correctly; siblings and auth are the only unaddressed gaps.

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 is 3, but the description enriches the `page` parameter meaningfully by confirming real page-based pagination and defining the out-of-range outcome, which the schema does not state. The `term` semantics are only restated.

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 Zappos's product catalog by keyword'), so an agent immediately knows this is the free-text entry point. It does not name any sibling (e.g. zappos_product for detail lookup, zappos_suggest for autocomplete), so differentiation is only implied by 'by keyword'.

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 'search ... by keyword', and the pagination note hints at iterating pages. However there is no explicit when-to-use or when-not guidance versus zappos_product, zappos_brand, or zappos_suggest.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.