Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

colehaan_product_recommendations

Fetch Cole Haan product recommendations by product handle, resolving it to a Shopify product ID and returning normalized related or complementary items with an optional limit.

Instructions

List Cole Haan product recommendations. Returns normalized recommended products for one Cole Haan (https://www.colehaan.com) product handle. The route handle is resolved to a Shopify product id before fetching recommendations. The storefront URL is fixed server-side.

Input Schema

TableJSON 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?

No annotations are provided, so the description must carry the burden. It discloses that the handle is resolved to a Shopify product id and that the storefront URL is fixed server-side, which are useful behavioral details. However, it doesn't state whether the operation is read-only or if there are any side effects, which is a gap for a tool that might be expected to be read-only.

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?

The description is three sentences, each serving a purpose. It front-loads the main action, then provides implementation details. No filler or redundancy.

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 tool with three parameters and no output schema, the description covers the key points: what it returns, how the handle is processed, and that the URL is fixed. It doesn't explain the return structure or pagination, but that's acceptable given the schema covers parameters. Overall, it's sufficient for an agent to understand the tool's function.

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 each parameter is documented. The description adds that the handle is resolved to a Shopify product id, which adds context for the handle parameter, but doesn't elaborate on limit or intent beyond schema. Since coverage is high, baseline 3 is 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?

Description states 'List Cole Haan product recommendations' with a clear verb and resource. It specifies it's for one product handle, distinguishing from colehaan_product and colehaan_products. However, it doesn't explicitly differentiate from other brand recommendation tools, but it's clear in context.

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 on when to use this tool vs alternatives. There are many similar recommendation tools in the sibling list, but the description doesn't mention them or provide selection criteria. It only describes what it does, not when to choose it.

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