Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stevemadden_page

Fetch a Steve Madden static page by handle to retrieve its title, URL, cleaned text, and timestamps. Unknown handles return 404.

Instructions

Get a Steve Madden static page. Returns one Steve Madden static page by its handle: id, title, URL, plain-text content and the created, published and updated timestamps. Page text is cleaned, not raw HTML. An unknown handle returns 404. When the reduced form is served, transport_mode is ssr_embedded and id is omitted.

Input Schema

NameRequiredDescriptionDefault
handleYesPage handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4/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 lists returned fields, clarifies content is cleaned plain text rather than raw HTML, states 404 behavior for unknown handles, and discloses the reduced-form transport_mode ssr_embedded case where id is omitted. Missing only auth or rate-limit context.

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, followed by return fields, cleaning note, error case, and reduced-form caveat. Every sentence carries information, though the reduced-form sentence is slightly dense.

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

Completeness5/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 fully compensates by enumerating the returned fields, the content-cleaning behavior, the error case, and the transport variant, leaving nothing essential unclear for a one-parameter lookup tool.

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 the single handle parameter is documented in the schema; the description adds only the notion of looking up 'by its handle' without format or example detail, so it does not meaningfully exceed the schema.

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 ('Get a Steve Madden static page... Returns one Steve Madden static page by its handle'), and the singular 'one page by its handle' clearly distinguishes it from the plural listing sibling stevemadden_pages.

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 usage context (retrieve a single page keyed by handle) is implied, and it notes that an unknown handle returns 404, but there is no explicit when-to-use versus the plural stevemadden_pages or other alternatives.

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