Crawlora MCP

zappos_brand

Read-only

Browse a Zappos brand page's product grid, with real page-based pagination and filterable facets. brand accepts a full brand URL, the "slug/id.zso" path from that URL, or just the opaque id from a zappos_brands result. An unrecognized brand returns not found.

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": {
      "brand": "<brand>"
    },
    "name": "zappos_brand"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Result page, 1-based, defaults to 1
`brand`	Yes	Zappos brand URL, slug/id.zso path, or opaque id

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 / brand / description
```
Added value: +"Zappos brand URL, slug/id.zso path, or opaque id"
```
- addedInput schema / properties / page / description
```
Added value: +"Result page, 1-based, defaults to 1"
```
First observedOct 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond them: it discloses that pagination is 'real page-based', that facets are filterable, and that an unrecognized brand returns 'not found', which is useful error-behavior context.

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 tightly written sentences: the capability and pagination are front-loaded, followed by the accepted input forms and error behavior. No filler text.

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 adequately covers pagination, facet filtering, accepted inputs, and the not-found case. It is essentially complete for a read-only browse tool.

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 description's explanation of 'brand' (full URL, slug/id.zso path, opaque id) merely restates what the schema's parameter description already says. It adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb ('Browse') and resource ('a Zappos brand page's product grid'), and distinguishes itself from siblings by tying the input to a zappos_brands result. An agent can tell this apart from zappos_search or zappos_brands without inspecting either schema.

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?

It implies the workflow by noting the brand id comes 'from a zappos_brands result', which hints when to use this tool, but it never explicitly states when to prefer it over zappos_search or when not to use it. Usage is implied rather than spelled out.

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.

Resources

Need Help?