Crawlora MCP

zappos_brands

Read-only

List Zappos brands discovered from Zappos's own published sitemap: id, a derived display name, slug, and url for each. Pair a returned id or url with zappos_brand to browse that brand's product grid. q, if set, case-insensitively filters to brands whose derived name or slug contains it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zappos_brands"
  }
}

Input Schema

Name	Required	Description
`q`	No	Case-insensitive substring filter on name or slug
`page`	No	Result page, 1-based, defaults to 1
`page_size`	No	Results per page, defaults to 100, max 1000

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.

Changed3 schema fields changedOct 7, 2026
- addedInput schema / properties / page / description
```
Added value: +"Result page, 1-based, defaults to 1"
```
- addedInput schema / properties / page_size / description
```
Added value: +"Results per page, defaults to 100, max 1000"
```
- addedInput schema / properties / q / description
```
Added value: +"Case-insensitive substring filter on name or slug"
```
First observedOct 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: the data comes from a published sitemap and the display name is 'derived', warning the agent not to expect an official canonical brand name. It does not discuss pagination behavior, which is left to the schema.

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?

Three tight sentences: identity/provenance first, then the follow-up tool, then the filter. Zero filler and every clause carries information an agent uses.

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?

With an output schema present, the description needn't explain return values, and it still names the fields and provenance. It covers purpose, source, filter, and the natural next call. Only pagination semantics are absent, which the schema supplies.

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 coverage is 100% and the schema already documents q, page, and page_size. The description restates q's filter semantics ('case-insensitively filters to brands whose derived name or slug contains it') with only the marginal addition that the name searched is the derived one. page/page_size get no description-level treatment. Baseline 3 fits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List Zappos brands'), the provenance ('discovered from Zappos's own published sitemap'), the exact fields returned, and the derived nature of the display name. An agent can tell this apart from zappos_brand and zappos_search without opening a schema.

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?

Explicitly routes the agent: 'Pair a returned id or url with zappos_brand to browse that brand's product grid' tells the agent what to do next with the output. It stops short of stating when NOT to use it versus sibling search/browse tools, so it's clear context without exclusions.

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.