Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brooklinen_product_recommendations

Get product recommendations for a Brooklinen item using its handle, with related or complementary intent and a configurable result limit.

Instructions

List Brooklinen product recommendations. Returns recommended products for one Brooklinen (https://www.brooklinen.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

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully states that the storefront URL is fixed server-side, implying no URL argument is needed, and 'List/Returns' implies a read-only operation. It does not describe authentication needs, rate limits, pagination, or failure behavior.

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 two short sentences and front-loads the main action: listing recommendations. The second sentence adds scope and the fixed-URL detail without unnecessary repetition, though the URL inclusion is marginally extraneous.

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 simple read-only recommendation tool with full schema description coverage and no output schema, the description is mostly complete. It states what is returned and that the URL is fixed, though it could say more about how recommendations are selected or how the intent parameter affects results.

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 handle, limit, and intent. The description only clarifies that recommendations are for one product handle and that the URL is fixed server-side, adding little parameter meaning beyond the structured schema.

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 states a specific verb and resource: it lists/returns recommended products for one Brooklinen product handle. It identifies the scope as a single handle and mentions the fixed storefront URL, but it does not explicitly distinguish this tool from sibling recommendation tools or nearby Brooklinen product tools.

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 implied by the phrase 'for one Brooklinen product handle,' which tells the agent that a product handle is required. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative such as brooklinen_product or brooklinen_products.

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