Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chewy_product_reviews

Get paginated Chewy product reviews by numeric ID. Fetch the full review set with sorting and positive/negative filters, including ratings, titles, authors, dates, and helpful counts.

Instructions

List a Chewy product's customer reviews, paginated. Returns one page of a Chewy product's customer reviews -- rating, title, body, author, submission date, helpful count, incentivized flag, and contributor badge -- with sorting and positive/negative filtering. chewy_product embeds only the first 20 reviews with no way to page past them; this endpoint reaches the whole set (products routinely carry thousands). id is the numeric id from any chewy.com PDP URL, and reviews are shared across a product's variants, so any variant's id returns the same set. total is the count for the current filter, so it drops when filter is applied, while rating_count stays the product's overall rating tally.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe numeric id from a chewy.com PDP URL, e.g. \
pageNoPage number, 1-based (default 1).
sortNoSort order. One of MOST_RELEVANT, NEWEST, OLDEST, HIGHEST_RATING, LOWEST_RATING, PHOTOS. Defaults to Chewy's own ordering when omitted.
limitNoReviews per page, 1 to 50 (default 20).
filterNoRestrict to POSITIVE (4-5 star) or NEGATIVE (1-3 star) reviews. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / filter / enum
      Added value: +[
+  "POSITIVE",
+  "NEGATIVE"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "MOST_RELEVANT",
+  "NEWEST",
+  "OLDEST",
+  "HIGHEST_RATING",
+  "LOWEST_RATING",
+  "PHOTOS"
+]
  2. Addedv1.16.2

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations to carry the safety/behavior burden, the description compensates fully. It discloses pagination, sorting and filtering options, the fields returned, and the semantics of total (filter-dependent) versus rating_count (overall). This goes well beyond a simple 'get reviews' statement.

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 compact sentences deliver a high information density with zero filler. The core function is front-loaded, and every clause earns its place: pagination, fields, comparison to the sibling, id semantics, and filter-aware counts.

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?

Given there is no output schema, the description generously lists the returned fields (rating, title, body, author, submission date, helpful count, incentivized flag, contributor badge). It also covers defaults, pagination, filtering, and the variant-id quirk, leaving the agent with no critical gaps for making a correct call.

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%, so the baseline is 3. The description adds meaning beyond the schema by explaining that id comes from a PDP URL and that reviews are shared across variants. It also clarifies the relationship between total and filter, which is not evident from the schema alone.

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 opens with 'List a Chewy product's customer reviews, paginated,' a specific verb-resource pair. It immediately distinguishes itself from the embedded reviews in chewy_product by stating 'chewy_product embeds only the first 20 reviews... this endpoint reaches the whole set,' making the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the sibling tool chewy_product and provides the exact condition for choosing this endpoint: when you need more than the first 20 reviews or need pagination. It also clarifies that any variant's id returns the same review set, guiding correct id usage.

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