Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rebag_search_suggest

Fetch Rebag predictive search suggestions for products, collections, and queries by passing a search term. Set result limits and choose suggestion types.

Instructions

Get Rebag search suggestions. Returns products, collections, and query suggestions from Rebag's (https://shop.rebag.com) predictive search. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoMaximum results per type, defaults to 10 and supports up to 20
typesNoComma-separated suggestion types. Allowed values: product, collection, query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

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 discloses that the storefront URL is fixed server-side and names the entity types returned. However, it does not mention read-only safety, rate limits, authentication requirements, or response format, leaving gaps for a suggest endpoint.

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. The third sentence about the fixed storefront URL earns its place by preventing an assumption that a URL parameter is needed. No wasted words, though the middle sentence could be slightly tighter.

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?

Given a simple suggest tool with a fully described 3-parameter schema and no output schema, the description is nearly complete. It states what is returned and clarifies the fixed server-side URL. The lack of explicit usage guidance is a separate dimension and does not make the description itself insufficient for calling the tool correctly.

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%: q, limit, and types are fully documented in the schema. The description mentions the suggestion types that correspond to the 'types' parameter, offering minor reinforcement, but adds no syntax, constraints, or defaults beyond the schema. Baseline 3 applies.

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 'Get' and resource 'Rebag search suggestions'. It further clarifies the returned types (products, collections, query suggestions) and that they come from predictive search. This distinguishes it from a generic search like rebag_search, though it does not explicitly name a sibling alternative.

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?

The description does not state when to use this tool versus alternatives such as rebag_search or rebag_products. 'Predictive search' strongly implies an autocomplete/typeahead use case, but no explicit conditions, exclusions, or prerequisites are given. Usage is implied rather than documented.

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