Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

colehaan_page

Fetch a Cole Haan static page by handle to get its ID, title, URL, plain-text content, and created, published, and updated timestamps; unknown handles return 404.

Instructions

Get a Cole Haan static page. Returns one Cole Haan static page by its handle: id, title, URL, plain-text content, and created, published and updated times. A missing handle returns 404. When transport_mode is ssr_embedded, id is omitted and the content is plain text taken from the page's rich-text blocks.

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 full burden and does well: it discloses the 404 behavior on a missing handle and the mode-dependent output shape (id omitted for ssr_embedded, content sourced from rich-text blocks). It omits auth requirements and rate limits, which is a minor gap.

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?

Three front-loaded sentences: purpose, return shape plus error behavior, then the edge-case caveat. Every sentence carries distinct information with no filler.

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 compensates by listing returned fields, error behavior, and the ssr_embedded variance. It stops short of auth/permission context, but for a simple read-by-handle tool it is largely self-sufficient.

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 there is one parameter, so the schema already documents `handle` as 'Page handle.' The description adds return-field semantics but nothing about handle format or derivation. The mention of `transport_mode` describes an undocumented parameter's effect on output rather than the declared input.

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 Cole Haan static page") and immediately enumerates the returned fields, making it clearly distinct from sibling list tools like colehaan_pages. An agent can identify the fetch-one-by-handle operation without opening the schema.

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 single-resource retrieval via 'by its handle' and implicitly contrasts with the plural colehaan_pages listing tool, but never explicitly states when to use this versus alternatives or any prerequisites. Usage is inferable but not guided.

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