Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

colehaan_products

List Cole Haan products from the catalog with page and limit options, returning paginated JSON for browsing or data use.

Instructions

List Cole Haan products. Returns products from Cole Haan's (https://www.colehaan.com) product catalog. The storefront URL is fixed server-side. Valid empty result pages return 200 with an empty products array.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose two useful traits: the storefront is fixed server-side (no store param needed) and empty pages return 200 with an empty products array. It omits auth/permission needs, mutation safety (implied read but not stated), and rate-limit behavior, so 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.

Conciseness4/5

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

Three short sentences, front-loaded with the core action and with no filler. Each sentence carries distinct information (action, catalog scope, edge-case behavior), though the URL citation is marginally redundant with the tool name.

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?

For a two-param read-only list tool with no output schema and no annotations, the description covers the storefront scope and empty-result edge case but leaves out usage routing and any behavioral context beyond that. Adequate but with clear gaps.

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%: page (1-based, default 1) and limit (default 50, max 250) are already fully documented in the schema. The description adds nothing about pagination semantics or how page/limit interact, 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 products') and pins the scope to a fixed external catalog. However, it does not distinguish itself from siblings like colehaan_product (single item) or colehaan_collection_products (collection-scoped), so an agent can't tell from the description alone whether this is the full-catalog list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance, and no mention of the obvious alternatives (colehaan_collection_products, colehaan_search_suggest, colehaan_product). The one contextual line ('storefront URL is fixed server-side') is scope info, not 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