Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chewy_product

Retrieve full details for a Chewy product using its numeric ID. Returns name, brand, description, images, price, stock, rating, reviews, Q&A, promotions, and shipping data.

Instructions

Get a Chewy product's detail. Returns one Chewy product's full detail: name, brand, description, images, price, stock, rating and its star-count breakdown, category breadcrumbs, customer questions and answers, and customer reviews. id is the numeric id from a chewy.com PDP URL, e.g. 185468 from https://www.chewy.com/frisco-lion-mane-dog-cat-costume/dp/185468 -- also the same value a chewy_category response's products[].part_number field carries for that product's own default variant. The response also carries the item's shipping weight and package dimensions as Chewy states them, its per-order purchase limit, and any promotions currently attached to it (each with a type such as "Spend $X" or "BOGO", plus short and long descriptions).

Input Schema

NameRequiredDescriptionDefault
idYesNumeric id from a chewy.com PDP URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.3/5.0
Behavior4/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 disclose the response payload in unusual detail (including non-obvious fields like shipping weight, package dimensions, per-order purchase limit, and promotion objects with type/short/long descriptions). The read-only nature is clearly implied by 'Get'/'Returns', though it never states permissions, rate limits, or failure behavior for an invalid id.

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?

Front-loaded correctly and every sentence carries information, including return-field coverage that compensates for the absent output schema. The only waste is the mild redundancy of 'Get a Chewy product's detail. Returns one Chewy product's full detail:', and the final sentence is a long list-heavy clause.

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-parameter, read-only detail tool with no output schema, the description supplies both the id provenance and a full inventory of return fields, including the unusual promotion and shipping attributes. Nothing essential an agent needs to call it correctly is missing, aside from minor error-handling that is not expected of a description this short.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description goes well beyond it: it fixes the id as numeric, gives a worked example (185468 from the PDP URL), and identifies the equivalent field (chewy_category products[].part_number for the default variant). That is exactly the kind of tracing information the schema alone cannot convey.

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?

Opens with a specific verb+resource ('Get a Chewy product's detail') and then enumerates exactly what comes back (name, brand, price, stock, ratings breakdown, breadcrumbs, Q&A, reviews, shipping/dimensions, purchase limit, promotions), which implicitly separates it from single-resource siblings like chewy_product_reviews or chewy_product_questions. An agent knows this is the full detail endpoint, not a search or list.

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?

There is no explicit when-to-use / when-not statement or named alternative, but the description does route usage indirectly by telling the agent where the id comes from: a chewy.com PDP URL or a chewy_category response's products[].part_number. That is enough to imply the call context, but it never says when this tool should be preferred over chewy_products, chewy_variants, or the dedicated review/question tools.

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