Crawlora MCP

stevemadden_pages

Read-only

Returns normalized static pages from Steve Madden (https://www.stevemadden.com). The storefront URL is fixed server-side. limit: Maximum static pages to return. Default 50, maximum 250. page: 1-based page number, default 1. Use stevemadden_page to get a Steve Madden static page.

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": "stevemadden_pages"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	1-based page number, default 1.
`limit`	No	Maximum static pages to return. Default 50, maximum 250.

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.

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior3/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 one genuinely useful behavioral fact — the storefront URL is fixed server-side, meaning no URL parameter is needed — but discloses nothing about pagination termination, total counts, or normalization details beyond the word "normalized".

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded correctly, but two of the four sentences simply copy the schema descriptions for limit and page, which does not earn its place alongside structured fields. It is adequately sized with avoidable redundancy.

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 simple two-parameter, output-schema-backed read-only list tool, the description covers identity, scope, the fixed-URL constraint, and the sibling alternative. Nothing critical for correct invocation is missing.

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% and both parameters already carry their own defaults and maximums in the schema. The description merely restates the schema text for page and limit verbatim, adding no syntax, interaction, or edge-case meaning beyond structured data.

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 ("Returns normalized static pages from Steve Madden") and explicitly names the sibling it is not — stevemadden_page. An agent can distinguish the list tool from the single-page tool without opening 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The final sentence routes the agent to stevemadden_page for retrieving a single static page, which is the key sibling disambiguation. It stops short of telling the agent when NOT to paginate or any prerequisite conditions, so it is clear context but not a full when/when-not guide.

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?