Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pristine_marketplace_store

Fetch normalized Pristine Marketplace storefront metadata from credential-free JSON, using a fixed store URL and handling blocked /products.json via fallback sources.

Instructions

Get Pristine Marketplace store metadata. Returns normalized storefront metadata for Pristine Marketplace (https://www.pristinemarketplace.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.8/5.0
Behavior5/5

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

No annotations exist, so the description carries full responsibility. It discloses that data is credential-free, the URL is fixed, and that fallback sources are used if the vanity domain blocks /products.json, including discovered *.myshopify.com domains or embedded page data. This goes well beyond a generic 'get store metadata' statement.

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 sentences, front-loaded with the core purpose, then efficient expansion into fixed-URL and fallback behavior. No filler, and all details serve the agent's decision-making.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only metadata tool with no output schema, the description covers the essential elements: what is returned, where it comes from, that no credentials are needed, and what fallbacks occur. Agents have enough information to invoke and interpret the result.

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

Parameters5/5

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

With zero parameters, the empty schema is inherently complete, but the description adds value by explicitly stating that no url parameter is accepted because the storefront URL is fixed server-side. This prevents callers from attempting a url argument that sibling Shopify store tools might take.

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?

The description opens with a specific verb and resource: 'Get Pristine Marketplace store metadata.' It further clarifies the exact branded target and the normalized nature of the output, distinguishing this endpoint from product, collection, and generic store tools.

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?

The description clearly conveys that this is a brand-pinned wrapper around the generic Shopify store family with the URL fixed server-side, so callers know not to supply a url and should use this for Pristine Marketplace rather than a generic store endpoint. It does not name sibling alternatives explicitly, but the contextual guidance is strong enough to route selection.

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