Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brooklinen_product_recommendations

Get product recommendations for any Brooklinen product by handle. The tool resolves the handle to a Shopify ID, then returns normalized related or complementary items with an optional limit.

Instructions

List Brooklinen product recommendations. Returns normalized recommended products for one Brooklinen (https://www.brooklinen.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.1/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 full burden. It discloses that the handle is resolved to a Shopify product ID and that the storefront URL is fixed server-side, which is useful context. However, it doesn't state whether the operation is read-only, requires authentication, or describe error conditions or response format details. It implicitly suggests a read operation but doesn't make it explicit.

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?

The description is concise with three sentences, front-loading the purpose. It avoids fluff and technical details are brief. The inclusion of the URL and resolution details is useful but not overdone. It earns a high score for clarity and economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should clarify the return structure. It only says 'normalized recommended products,' which is vague. It also doesn't mention that limit and intent are optional, nor does it explain what 'normalized' means or potential errors. For a simple tool with 3 parameters, it lacks sufficient detail for an agent to confidently invoke it without additional assumptions.

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 baseline is 3. The description doesn't add any additional meaning to the parameters beyond what the schema already provides; it simply reiterates that a handle is required. It doesn't explain limit or intent semantics beyond their schema descriptions.

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 clearly states the tool lists Brooklinen product recommendations for a given product handle, which is a specific verb+resource. It distinguishes itself from siblings like brooklinen_product by focusing on recommendations, though it doesn't explicitly name alternatives.

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?

The description provides no explicit guidance on when to use this tool versus other Brooklinen tools (e.g., brooklinen_product, brooklinen_products). It doesn't mention when not to use it or any alternatives, leaving the agent to infer from the tool name and context.

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