Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rebag_products

Fetch normalized product listings from Rebag's public catalog with pagination and customizable limits, returning clean JSON for e-commerce data retrieval.

Instructions

List Rebag products. Returns normalized products from Rebag's (https://shop.rebag.com) public product catalog. The storefront URL is fixed server-side. Valid empty result pages return 200 with an empty products array.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum products, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the storefront URL is fixed server-side and that valid empty result pages return 200 with an empty products array. This is useful behavioral context beyond the schema, though it doesn't detail pagination behavior or rate limits.

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 sentences with no waste. The core action is front-loaded, and the behavioral notes are concise. Every sentence earns its place.

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?

For a simple list tool with two optional parameters and no output schema, the description covers the essentials. However, it doesn't mention what fields the normalized products contain, which could matter for an agent deciding whether this tool fits. The empty-page behavior is a nice touch but doesn't fully compensate for the lack of return-value context.

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 both parameters (page and limit). The description adds no additional parameter semantics beyond what the schema provides. Baseline 3 is appropriate.

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 ('List') and resource ('Rebag products'), and clarifies it returns normalized products from Rebag's public product catalog. It doesn't explicitly differentiate from sibling tools like rebag_product or rebag_search, but the resource and scope are clear enough.

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 implies usage context (listing products from Rebag's public catalog) but doesn't explicitly state when to use this tool versus alternatives like rebag_product or rebag_search. The fixed storefront URL note is useful but doesn't provide exclusions or alternative routing.

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