Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pristine_marketplace_pages

Lists static Pristine Marketplace pages, including Shop by Sport landings for NFL, MLB, NBA, NHL, and NASCAR, with page and limit controls.

Instructions

List Pristine Marketplace static pages. Returns normalized static pages from Pristine Marketplace (https://www.pristinemarketplace.com). The storefront URL is fixed server-side. The storefront's "Shop by Sport" navigation (NFL, MLB, NBA, NHL, NASCAR) resolves to pages here (handles nfl, mlb, nba, nhl, nascar), not to a separate collections-style resource -- each is a landing page linking into many player/team collections.

Input Schema

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

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 provided, the description carries the full burden. It discloses that the storefront URL is fixed server-side, that sport navigation handles resolve to pages here rather than a separate collections resource, and that each is a landing page linking into collections. This adds meaningful behavioral context beyond the basic 'list pages' function, though it doesn't detail pagination behavior or response format.

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?

The description is reasonably concise and front-loaded with the core purpose. The additional context about the storefront URL and sport navigation is valuable and earns its place, though it could be slightly more compact.

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 list tool with two optional parameters and no output schema, the description provides sufficient context about what the resource is and how it relates to the storefront's navigation. It doesn't explain return value structure, but with no output schema and a simple list operation, the description is largely complete for an agent to invoke it correctly.

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) with their defaults and limits. The description doesn't add additional parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 clearly states the tool lists Pristine Marketplace static pages, names the specific storefront URL, and explicitly distinguishes this resource from a collections-style resource by explaining that 'Shop by Sport' navigation resolves to pages here. This differentiates it from sibling tools like pristine_marketplace_collections and pristine_marketplace_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?

The description provides clear context about what the tool returns and how the storefront's navigation maps to these pages, which helps an agent understand when to use it. However, it doesn't explicitly state when to use this tool versus alternatives like pristine_marketplace_page or pristine_marketplace_collections, nor does it mention exclusions.

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