Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

colehaan_products

Fetch normalized Cole Haan products from the public catalog for ecommerce research, using page and limit parameters to control results.

Instructions

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

Input Schema

TableJSON 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.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose that results are normalized, the storefront URL is fixed server-side, and empty result pages return 200 with an empty products array. However, it does not describe pagination behavior beyond the schema, error cases, or what fields 'normalized products' includes.

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 sentences with the purpose front-loaded and no filler. The URL, normalization note, and empty-page behavior are all substantive details that help an agent invoke the tool correctly.

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 2-parameter, zero-required list tool with no output schema, the description is fairly complete: it gives the source, normalization behavior, fixed URL, and an edge case. It lacks explicit mention of return-field details and pagination semantics, but those are not critical for a simple catalog list operation.

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?

The input schema covers 100% of parameters (page, limit), so the baseline is 3. The description adds no further semantics about how page and limit behave, such as what happens when limit exceeds 250 or how page bounds are enforced.

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?

The description opens with 'List Cole Haan products', a specific verb and resource, and clarifies the source as Cole Haan's public product catalog with a server-side fixed storefront URL. It is clear about what the tool does but does not explicitly contrast with sibling tools like colehaan_product or colehaan_collection_products, so the distinction is left to inference.

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 guidance is provided on when to use this tool versus alternatives such as colehaan_product, colehaan_collection_products, or colehaan_search_suggest. The description only states what the tool does, not the conditions that would make it the right choice.

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