Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

quince_product_reviews

Fetch Quince product reviews by handle to see 25 sampled customer reviews, overall rating, and review count for a product.

Instructions

Get Quince product reviews. Returns a sample of a Quince product's customer reviews (author, date, rating, review body), plus the product's overall aggregate rating and review count. handle is the same value quince-product accepts. The reviews returned are a sample (25 reviews on every product sampled), not a paginated feed of the full review history. A product with no reviews yet returns a well-formed empty result.

Input Schema

NameRequiredDescriptionDefault
handleYesProduct URL handle, from a search result's products[].handle field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses that results are a fixed 25-review sample rather than a paginated feed, describes the shape of each returned review, reports the aggregate rating/count, and covers the empty-result edge case ('a product with no reviews yet returns a well-formed empty result'). This is exactly the behavioral context an agent needs before invoking.

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?

Front-loaded with the core purpose, then progressively adds return contents, the handle linkage, the sampling caveat, and the empty-case. Every sentence conveys distinct information; nothing is redundant padding.

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?

There is no output schema, so the description must describe returns — and it does, listing the review fields plus aggregate rating and count, and noting the sample size and empty-result behavior. An agent has everything needed to call and interpret this 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 coverage is 100% and the single handle parameter is fully documented in the schema as coming from a search result's products[].handle. The description adds a useful cross-tool note ('same value quince-product accepts'), but this largely overlaps the schema's own sourcing hint, so the baseline 3 for high-coverage schemas 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?

States a specific verb and resource ('Get Quince product reviews') and immediately enumerates what comes back (author, date, rating, review body plus aggregate rating and count). It also ties itself to the sibling quince-product by naming the shared handle value, so an agent can distinguish it from quince_product, quince_product_faq, and quince_search without opening a 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?

The description routes the agent by explaining that 'handle is the same value quince-product accepts,' which is the key precondition for calling it. It does not, however, explicitly state when to prefer this over quince_product_faq or the product tool, so there is no exclusion guidance — clear context but no alternatives spelled out.

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