Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stevemadden_pages

List Steve Madden static pages with pagination, returning handle, title, URL, plain-text content, and timestamps for each page.

Instructions

List Steve Madden static pages. Lists Steve Madden static pages, 50 per request by default (limit up to 250), with page starting at 1. Each page has its handle, title, URL, plain-text content and timestamps. An empty result is a normal 200. When transport_mode is ssr_embedded, items carry only handle, url and updated_at.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses default page size (50), the 250 cap, 1-based paging, returned fields, that an empty result is a normal 200, and that ssr_embedded transport yields a reduced field set. It omits auth/rate-limit context, but the return-shape and edge-case disclosure is genuinely useful.

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?

Front-loaded with the core action and then layered with pagination and return details. The first two sentences redundantly repeat 'List Steve Madden static pages', a minor waste, but the overall shape is efficient.

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?

No output schema exists, so the description appropriately documents the returned fields (handle, title, URL, content, timestamps) and the ssr_embedded variant. Pagination and empty-result behavior are covered, leaving little an agent would need beyond this.

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%, so both `page` and `limit` are already documented in the schema. The description restates the same defaults and caps without adding syntax or format detail, so the baseline 3 applies.

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 static pages'), clearly distinguishing the resource from siblings like stevemadden_products or stevemadden_collections. It does not explicitly name the singular stevemadden_page detail sibling, but the scope is unambiguous.

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?

Usage is implied by the resource ('static pages'), but the description never states when to choose this over stevemadden_page or stevemadden_sitemaps, nor any exclusions. Adequate but with a clear gap in routing guidance.

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