Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stevemadden_products

List Steve Madden products from the public catalog with page and limit controls, returning structured JSON for catalog browsing or e-commerce research.

Instructions

List Steve Madden products. Returns products from Steve Madden's (https://www.stevemadden.com) public product catalog. The storefront URL is fixed. Valid empty result pages return 200 with an empty products array.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum products, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that results come from a fixed public storefront and that empty result pages still return 200 with an empty array, which helps an agent interpret responses. However, it omits auth/rate-limit behavior and how deep pagination behaves.

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?

Three short sentences, front-loaded with the core action, then scope, then the empty-result edge case. Nothing is redundant or padded, though the middle sentence is slightly repetitive of the first.

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 no output schema and no annotations, the description still conveys the return shape (a products array) and the empty-page status behavior, and the schema covers pagination. It is adequate for a simple listing tool, with only minor gaps around pagination depth and response richness.

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% for both page and limit (including the 1-based default and the 250 cap), so the schema already documents them fully. The description adds no extra semantics for either parameter, making the baseline 3 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+resource ('List Steve Madden products') and scopes it to the public product catalog at a fixed storefront URL. An agent can distinguish it from the singular stevemadden_product detail tool by the plural 'list' framing, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description never says when to use this catalog-wide listing versus stevemadden_collection_products, stevemadden_product, or stevemadden_search_suggest. The only implicit guidance is that the storefront URL is fixed, meaning no store parameter is needed, but there is no explicit when-to-use or exclusion statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools