Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

colehaan_search_suggest

Retrieve Cole Haan predictive search suggestions, including products, collections, and queries, for a given search term. Set result limits and suggestion types to match your needs.

Instructions

Get Cole Haan search suggestions. Returns products, collections, and query suggestions from Cole Haan's (https://www.colehaan.com) predictive search. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoMaximum results per type, defaults to 10 and supports up to 20
typesNoComma-separated suggestion types. Allowed values: product, collection, query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but discloses only that results come from predictive search and that the storefront URL is fixed server-side. It does not state read-only status, authentication requirements, rate limits, error behavior, or whether suggestions are cached or live.

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 short sentences with the main action front-loaded and no redundant restatement. The fixed-URL note is compact and useful rather than filler.

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 simple 3-parameter autocomplete tool with no output schema, the description identifies the suggestion types returned but gives no shape for individual results. Combined with absent auth/rate-limit context, it is minimally adequate but leaves an agent guessing about output structure.

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%, so the schema already documents q, limit, and types with defaults and allowed values. The description adds no syntax, default, or filtering detail beyond what the schema provides, making the baseline 3 appropriate.

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 ("Get Cole Haan search suggestions") and enumerates the returned suggestion types, which helps distinguish it from product-list or product-detail siblings. It does not explicitly name an alternative tool, so sibling differentiation is implicit rather than explicit.

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?

Provides no when-to-use guidance, no when-not-to-use conditions, and no named alternatives among the many Cole Haan tools. The "predictive search" phrase hints at autocomplete use, but nothing tells the agent when to choose this over colehaan_products or colehaan_collections.

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