Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pristine_marketplace_reviews

Retrieve store-wide Pristine Marketplace reviews from Judge.me's public feed, sorted most recent first, with 5 reviews per page via a page parameter.

Instructions

List Pristine Marketplace store reviews. Returns one page of Pristine Marketplace's (https://www.pristinemarketplace.com) public Judge.me store review feed. This is a store-wide, most-recent-first feed, not a per-product one: confirmed live, the storefront's own on-page review widget draws from and displays this same feed (labeled "Reviews for other products" on an individual product page), and no product/handle filter parameter narrows it. The storefront URL is fixed server-side. Judge.me fixes 5 reviews per upstream page regardless of any requested size, so this endpoint has no limit parameter -- page maps 1:1 onto Judge.me's own pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1. 5 reviews per page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it excels: it discloses the public Judge.me source, the fixed server-side storefront URL, most-recent-first ordering, the 5-reviews-per-page cap, and explains why there is no limit parameter. It also provides live verification that the storefront widget uses the same feed.

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?

The description is front-loaded with the core purpose and every sentence earns its place: source, scope, pagination behavior, and the absence of a limit parameter are all relevant for correct invocation. Despite its length, there is no filler.

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 single-optional-parameter public read endpoint with no output schema, this is complete. An agent knows exactly what data it returns, how pagination works, why certain parameters do not exist, and how it differs from product-level reviews.

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?

The schema already fully documents the page parameter with 100% coverage, so the baseline is 3. The description adds meaningful nuance by explaining that page maps 1:1 onto Judge.me pagination, defaults to 1, and that no limit parameter exists because Judge.me fixes pages at 5 reviews.

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 states a specific verb and resource: it lists Pristine Marketplace's store-wide Judge.me review feed. It explicitly distinguishes itself from a per-product feed and notes that no product/handle filter narrows it, making its scope clear relative to sibling product 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 explains that this is the store-wide reviews endpoint, not a per-product one, and that there is no product filter. It does not name a specific sibling tool to use instead for product-specific reviews, but the context is strong enough that an agent would not misuse it.

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