Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stevemadden_sitemap_urls

List Steve Madden sitemap URLs by type (products, collections, pages, blogs, all) with a capped limit to gather storefront links for crawling or analysis.

Instructions

List Steve Madden sitemap URLs. Returns capped URL entries from Steve Madden's (https://www.stevemadden.com) child sitemaps matching the requested type. The storefront URL is fixed server-side.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoSitemap type. Allowed values: all, products, collections, pages, blogs, agentic_discovery, other
limitNoMaximum URL entries, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "all",
+  "products",
+  "collections",
+  "pages",
+  "blogs",
+  "agentic_discovery",
+  "other"
+]
  2. Addedv1.16.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose several behaviors: results are capped (aligned with limit), filtered by type, and the storefront URL is fixed server-side. However, it does not explicitly state read-only behavior, pagination, rate limits, or the exact nature of 'URL entries', so some transparency gaps remain.

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?

The description is concise and front-loaded, with three sentences each adding distinct value: purpose, return characteristics, and a server-side behavioral note. There is no filler, redundancy, or unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (two optional parameters, no output schema), and the description explains that it returns capped URL entries matching a requested type. However, it does not clearly specify the return structure (e.g., array of URL strings vs. objects), nor does it mention pagination or error behavior. While adequate for basic use, more detail on the return format would improve completeness.

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 baseline is 3. The description adds minor semantic context by linking 'type' to child sitemaps and ‘capped’ to the limit, but it does not meaningfully enhance the parameter meaning beyond what the schema already provides for limit's default and maximum.

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?

The description clearly states a specific verb and resource ('List Steve Madden sitemap URLs') and adds detail about child sitemaps and type matching. It does not explicitly contrast with sibling tools like stevemadden_sitemaps, but the storefront name and function are distinct enough that an agent can identify its purpose.

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?

The description implies when to use the tool (when you need Steve Madden sitemap URLs) but provides no explicit guidance about when not to use it or which sibling tool to choose instead. It does not mention alternatives such as stevemadden_sitemaps or stevemadden_products, leaving the selection largely to inference.

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