Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rebag_search

Search Rebag's product catalog by query and return ranked results with condition grade and colour, plus page, sort, and limit controls for browsing listings.

Instructions

Search Rebag products. Returns ranked products from Rebag's (https://shop.rebag.com) own full-text product search, including a best-effort condition grade and colour derived from the product's own catalog tags -- attributes not available from the other catalog endpoints in this family. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query text
pageNo1-based page, defaults to 1
sortNoSort order. Allowed values: relevance, price_asc, price_desc
limitNoMaximum products, defaults to 20 and supports up to 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that results are ranked, that condition grade is 'best-effort', that colour is derived from catalog tags, and that the storefront URL is fixed server-side (removing a decision the agent might otherwise try to make). It doesn't cover auth, rate limits, or pagination behavior, so not a 5.

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?

Two sentences, front-loaded with the core purpose before the differentiating detail and the server-side URL note. Efficient, with only mild density in the second sentence.

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 4-param read-only search with full schema coverage and no output schema, the description covers what it does, what makes its output special, and a data-quality caveat. It's adequate; only richer return-shape detail would push it higher.

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 q, page, sort, and limit are fully documented by the schema itself. The description adds no additional parameter detail (e.g., query syntax, sort default), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Search Rebag products') and immediately scopes it to Rebag's own full-text search, distinguishing it from the sibling catalog endpoints (rebag_products, rebag_collections, etc.). It also names the unique value (condition grade and colour) that differentiates this endpoint.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear implied guidance by noting it returns attributes 'not available from the other catalog endpoints in this family', which routes an agent to this tool when condition/colour matter. However, it never names a specific alternative or states an explicit when-not-to-use condition, so it stops short of full 5-level guidance.

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