Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pristine_marketplace_pages

Lists static pages from Pristine Marketplace, including Shop by Sport landing pages for NFL, MLB, NBA, NHL, and NASCAR that link into player and team collections.

Instructions

List Pristine Marketplace static pages. Returns 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

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

B3.3/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 adds useful behavioral context ('storefront URL is fixed server-side') and clarifies the sport nav resolves here rather than to a collections resource. It says nothing about pagination behavior, rate limits, or what the returned page objects contain.

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

Conciseness3/5

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

The first two sentences are largely redundant ('List Pristine Marketplace static pages' / 'Returns static pages from Pristine Marketplace'), wasting space. The distinctive Shop by Sport content comes last and does earn its place, but front-loading is weakened by the repetition.

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?

With no output schema and no annotations, the description must do more lifting. It covers what is returned and the sport-navigation quirk, but leaves the shape of returned pages and pagination semantics unstated, so it is only minimally complete for a listing tool.

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% for both parameters (page, limit), so the schema already documents defaults and limits. The description adds no syntax or format detail beyond that, making the baseline 3 correct.

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 specific verb and resource ('List Pristine Marketplace static pages') and distinguishes the output from a collections-style sibling resource. It doesn't mention the singular `pristine_marketplace_page` sibling, so differentiation is partial rather than complete.

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 Shop by Sport explanation implies when this tool is relevant (sport landing pages like nfl/mlb/nba), which is genuine usage context. However, there is no explicit when-to-use vs. `pristine_marketplace_page`, `pristine_marketplace_collections`, or `pristine_marketplace_store`, and no 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