Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pristine_marketplace_page

Fetch static page details for any Pristine Marketplace page handle, including Shop by Sport landing pages such as nfl, mlb, nba, nhl, and nascar.

Instructions

Get a Pristine Marketplace static page. Returns static page detail for one Pristine Marketplace (https://www.pristinemarketplace.com) page handle. The storefront URL is fixed server-side. The "Shop by Sport" nav landing pages are reachable here as handles nfl, mlb, nba, nhl, and nascar.

Input Schema

NameRequiredDescriptionDefault
handleYesPage handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/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 (so the agent knows it cannot target another domain) and gives valid handle examples. It does not state that this is a read-only operation, nor anything about response shape, pagination, or auth, leaving meaningful gaps.

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 short sentences, front-loaded with the purpose, then the return scope, then a concrete handle example. Efficient and free of padding, though the middle 'storefront URL is fixed server-side' sentence is somewhat tangential.

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 single-parameter read tool with no output schema, the description supplies the site, the return scope, and example handles — enough for an agent to call it correctly. It lacks any note on failure behavior for invalid handles, which keeps it from being fully complete.

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?

Schema coverage is 100% but the schema itself only says 'Page handle'. The description adds real meaning by enumerating concrete handle values (nfl, mlb, nba, nhl, nascar), telling the agent what a valid handle looks like — value the bare schema does not provide.

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?

The description gives a specific verb+resource ('Get a ... static page') and narrows scope to a single page handle, which distinguishes it from the plural listing sibling pristine_marketplace_pages. It stops short of explicitly naming siblings to differentiate from, so it's clear but not maximally sharp.

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?

It implies usage by giving concrete handle values ('nfl', 'mlb', ...) for the Shop by Sport nav pages, which shows when this tool is appropriate. However, it never states when to reach for pristine_marketplace_page vs pristine_marketplace_pages or pristine_marketplace_product, so the guidance is only implied.

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