Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rebag_products

List and paginate products from Rebag's public catalog by page and limit, returning clean JSON for product discovery.

Instructions

List Rebag products. Returns 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

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

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the storefront URL is fixed server-side and that empty result pages return 200 with an empty array — a real edge case. But it omits auth/permission needs, rate limits, and the safety profile of a read operation, so it adds partial value only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the purpose and catalog source, followed by the two most relevant operational facts. No filler; every sentence earns its place.

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 paginated listing tool with full schema coverage and no output schema, the description covers what is returned and the empty-page case. It could say more about the shape of a product record, but nothing essential to invoking it correctly is missing.

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 coverage is 100%, so both page and limit are fully documented in the schema (including the 1-based semantics and the 50/250 bounds). The description adds nothing about parameter behavior, so the baseline of 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 clear verb+resource ('List Rebag products') and specifies the data source as Rebag's public product catalog. However, it does not differentiate from the many sibling listing tools (rebag_product, rebag_search, rebag_collection_products), so an agent cannot tell from the description alone which Rebag entry point returns the full catalog versus a filtered list or single item.

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 gives no when-to-use guidance, no exclusions, and names no alternative. It never says to reach for this over rebag_search or rebag_product, leaving the agent to infer selection from the name alone.

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