Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

stevemadden_collections

Read-only

Returns normalized collections from Steve Madden (https://www.stevemadden.com). The storefront URL is fixed server-side. Valid empty result pages return 200 with an empty collections array. limit: Maximum collections to return. Default 50, maximum 250. page: 1-based page number, default 1. Use stevemadden_collection_products to list Steve Madden collection products.

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_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number, default 1.
limitNoMaximum collections to return. Default 50, maximum 250.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 real behavioral context beyond them: the storefront URL is fixed server-side, and valid empty pages return 200 with an empty array — a genuinely useful edge-case note for an agent parsing results.

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?

Purpose is front-loaded and the whole definition is a few tight sentences. The one inefficiency is re-stating the two parameter descriptions verbatim, which the schema already carries, but overall there is little waste.

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, return-value details need not be explained, and the description covers purpose, the complementary tool, and the empty-page behavior. It is complete enough for an agent to call correctly; only broader sibling differentiation is thin.

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 both parameters are already documented in the schema. The description restates the limit default/max and the 1-based page default, which duplicates rather than extends the schema, so the baseline of 3 is appropriate.

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 ('Returns normalized collections from Steve Madden') and points to the sibling that handles the complementary resource (stevemadden_collection_products). It is clear what it returns, though it doesn't distinguish itself from the broader stevemadden_products/stevemadden_pages siblings.

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?

Names an explicit alternative and the condition that selects it ('Use stevemadden_collection_products to list Steve Madden collection products'), giving a usable routing rule. It stops short of describing when/when-not relative to the other storefront siblings, but the core fork is 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 toolsInspect
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