Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

pristine_marketplace_search

Search Pristine Marketplace products using the storefront's full-text search, then page through fixed 16-item result sets for product data.

Instructions

Search Pristine Marketplace products. Returns products from Pristine Marketplace's (https://www.pristinemarketplace.com) own full-text search, distinct from /pristine-marketplace/search/suggest's predictive suggestions. The storefront URL is fixed server-side. Per-page size is fixed (16 products per page) and is not adjustable; limit is honored only as an upper bound on the returned page.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query text
pageNo1-based page, defaults to 1
limitNoMaximum products, defaults to 50 and supports up to 250, but never exceeds the storefront's own fixed 16-per-page grid

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden and does disclose non-obvious operational traits: fixed 16-per-page size, the storefront URL being fixed server-side, and limit acting only as an upper bound. It stops short of describing return format or error/auth behavior.

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 tight sentences, front-loaded with the core action and immediately followed by the sibling distinction and constraints. No filler; every sentence adds a distinct fact.

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?

No output schema exists, but the description covers the key invocation concerns: query, pagination mechanics, and the sibling alternative. Return-field detail is minimal, though the tool is a straightforward search so this is largely acceptable.

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 already 100%, so baseline is 3, but the description adds meaningful interpretation of `limit` as an upper bound rather than a page-size control and explains the fixed pacing. This clarifies how the parameters interact with the server's fixed grid.

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 and resource ('Search Pristine Marketplace products') and explicitly scopes it as the storefront's own full-text search, distinguishing it from the predictive-suggestion sibling. An agent can identify the tool's role without opening the schema.

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?

Names the alternative endpoint (`/pristine-marketplace/search/suggest`) and characterizes its behavior as predictive suggestions, giving a clear basis for choosing between them. It does not, however, spell out broader when-to-use conditions beyond that single contrast.

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