Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

colehaan_product_recommendations

Fetch related or complementary Cole Haan product recommendations by product handle, with an optional limit.

Instructions

List Cole Haan product recommendations. Returns recommended products for one Cole Haan (https://www.colehaan.com) product handle. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum products, defaults to 10 and supports up to 20
handleYesProduct handle
intentNoRecommendation intent. Allowed values: related, complementary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / intent / enum
      Added value: +[
+  "related",
+  "complementary"
+]
  2. 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 carries the full burden. It does disclose one useful behavioral fact the schema cannot express: the storefront URL is fixed server-side, so no domain/host parameter is needed. It says nothing about pagination, ordering, or whether results are capped beyond the schema's limit note.

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, purpose front-loaded. The second sentence largely restates the first, but the third sentence (fixed server-side URL) earns its place by removing an anticipated parameter question.

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 3-parameter, no-annotation, no-output-schema tool, the description covers identity and the fixed-URL detail but is silent on result shape and ordering. Adequate but leaves small gaps an agent would otherwise have to discover by calling.

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 handle, limit, and the related/complementary enum are already documented in structured data. The description adds only the nuance that exactly one handle is consumed; baseline 3 is appropriate when the schema does the heavy lifting.

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 product recommendations') and clarifies it operates on a single product handle. An agent can distinguish it from colehaan_product (single product detail) and colehaan_products (catalog list), though it never names those siblings explicitly.

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?

Usage is only implied by the mention of 'one Cole Haan product handle'. There is no statement of when to prefer this over colehaan_product_related-style alternatives, nor any prerequisite guidance (e.g. handle must come from colehaan_product or search).

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