Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rebag_product_recommendations

Fetches recommended Rebag products for a given product handle, letting you retrieve related or complementary item suggestions with a configurable limit.

Instructions

List Rebag product recommendations. Returns recommended products for one Rebag (https://shop.rebag.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. Addedv1.17.5

TDQS

B3.2/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 burden. It usefully discloses that the storefront URL is fixed server-side, which tells the agent it cannot target other stores, and 'List/Returns' implies a read operation, but it omits auth needs, rate limits, pagination, and result ordering.

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, front-loaded with the core purpose, with the URL-scoping caveat placed after the main statement. Nothing is redundant, though the parenthetical URL is slightly incidental.

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?

There are no annotations and no output schema, so the description must cover more than it does. It conveys purpose and the server-side URL constraint but says nothing about what a recommendation record contains or how results are ordered, leaving a gap for a tool with zero structured metadata.

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 limit, handle, and intent are already documented in the schema. The description adds only that recommendations are tied to 'one product handle', which mildly reinforces the required handle but adds no meaning beyond the schema baseline.

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 (List/Returns) and resource (Rebag product recommendations) and scopes it to 'one Rebag product handle', which is precise enough to separate it from rebag_product or rebag_products. It stops short of naming a sibling to route between, so it is clear but not fully differentiated.

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 says what it returns but never states when to use it versus alternatives like rebag_product or rebag_search, and gives no prerequisites or exclusion conditions. Usage is only implied by the 'recommendations' framing.

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