Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rebag_store

Fetch Rebag store metadata from public Shopify JSON. Returns normalized storefront data like products and shop info without needing a URL or login.

Instructions

Get Rebag store metadata. Returns normalized storefront metadata for Rebag (https://shop.rebag.com), sourced from credential-free storefront JSON. This endpoint is a brand-pinned wrapper around the generic Shopify store family: the storefront URL is fixed server-side, so no url parameter is accepted. If the vanity domain blocks /products.json, the service may fall back to a public *.myshopify.com domain discovered from the storefront page, or to the storefront's own embedded page data for storefronts that expose neither.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the credential-free JSON source, the fixed storefront URL, and the fallback chain when /products.json is blocked (myshopify.com or embedded page data). It does not describe the exact metadata fields returned or behavior when all fallbacks fail.

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, front-loaded with the core purpose followed by positioning and fallback detail. Every sentence earns its place, though the fallback sentence is dense and could be slightly tightened.

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 zero-param, no-output-schema metadata endpoint, the description covers purpose, data source, URL binding, and fallback behavior. It does not enumerate the returned metadata fields, but an agent can invoke the tool correctly with the information provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, which sets a baseline of 4. The description adds meaningful context by explicitly stating that no url parameter is accepted because the URL is fixed server-side, preventing an agent from attempting to pass a parameter learned from the generic Shopify store siblings.

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 (Get) and resource (Rebag store metadata), identifies the exact URL (https://shop.rebag.com), and frames itself as a brand-pinned wrapper around the generic Shopify store family. This clearly distinguishes it from siblings like shopify_store and rebag_products.

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?

Explicitly explains this is a brand-pinned wrapper with a fixed server-side URL and that no url parameter is accepted, making it clear when to choose this over the generic Shopify store tool. It does not name specific sibling alternatives or state an explicit when-not-to-use, so it stops short of a 5.

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