Crawlora MCP

stevemadden_product_recommendations

Read-only

Returns normalized recommended products for one Steve Madden (https://www.stevemadden.com) product handle. The route handle is resolved to a Shopify product id before fetching recommendations. The storefront URL is fixed server-side. intent: Recommendation intent. Allowed values: related, complementary. Defaults to related. limit: Maximum recommended products to return. Default 10, maximum 20. Use stevemadden_product to get a Steve Madden product.

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": {
      "handle": "<handle>"
    },
    "name": "stevemadden_product_recommendations"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum recommended products to return. Default 10, maximum 20.
`handle`	Yes	Required. Seed product handle (URL slug) to base recommendations on.
`intent`	No	Recommendation intent. Allowed values: related, complementary. Defaults to related.

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.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds internal behavior (handle is resolved to a Shopify id before fetching, storefront URL is fixed server-side), but says nothing about pagination, rate limits, or what 'normalized' entails.

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?

The core behavior is front-loaded and readable, but it redundantly restates the intent and limit parameter descriptions already provided by the schema, which is mild 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 and annotations present, the description need not explain return values, and it covers the seed-handle prerequisite and resolution behavior. Complete enough for an agent to call it correctly, with only minor gaps around sibling selection.

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%, so the schema already documents handle, intent, and limit. The description merely repeats the intent enum and limit bounds verbatim, adding no new meaning beyond the structured fields.

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 recommended products') scoped to a single Steve Madden product handle. It also differentiates from the sibling stevemadden_product by noting that tool is for fetching a product, not for recommendations.

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?

Gives clear context: recommendations are seeded by a product handle, and it points to stevemadden_product as the way to obtain a product. It does not, however, state when to prefer this over other related-product siblings (e.g., stevemadden_products), so it stops short of full when/when-not guidance.

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?