Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

colehaan_pages

List Cole Haan static pages with page and limit controls, returning handle, title, URL, plain-text content, and timestamps for content audits or site mapping.

Instructions

List Cole Haan static pages. Lists Cole Haan static pages, with page (from 1) and limit (default 50, max 250). Each page has handle, title, URL, plain-text content and timestamps. If transport_mode is ssr_embedded, items carry only handle, url and updated_at, so fetch a single page for its content.

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.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it delivers useful behavioral detail: pagination defaults/max, the exact field set returned, and a conditional output-shape variance under ssr_embedded. It omits auth/rate limits, but for a public read list that is minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening is redundant – 'List Cole Haan static pages. Lists Cole Haan static pages...' – wasting a sentence. The remainder (pagination, fields, transport_mode caveat) is dense and front-loaded, so structure is adequate but not tight.

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?

For a two-parameter list tool with no output schema, the description covers pagination, returned fields, and the important ssr_embedded content caveat. Nothing an agent needs to call it correctly appears to be missing.

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 description largely restates what the schema already documents ('page' from 1, 'limit' default 50, max 250). It adds no syntax or edge-case meaning beyond confirming the schema, so 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 and resource ('List Cole Haan static pages') and implies the distinction from the singular colehaan_page sibling via 'List'. It does not explicitly name the sibling, so differentiation is inferential rather than stated.

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 a clear conditional rule: when transport_mode is ssr_embedded, items lack content, so 'fetch a single page for its content' – effectively routing the agent to colehaan_page. No general when-not guidance beyond this, but the key branch is covered.

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