Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

chewy_facets

Retrieve Chewy category or search refinement options with product counts. Use to narrow listings by brand, sub-category, diet, rating, and more before fetching products.

Instructions

List a Chewy category or search's refinement options. Returns the full set of refinement options (facets) a Chewy category or keyword search can be narrowed by -- brand, sub-category, lifestage, food form, breed size, special diet, health feature, flavor, ingredient, packaging type, price band, customer rating, and whichever other dimensions that listing exposes -- with each option's product count. No products are returned, so this is a much smaller call than chewy_category/chewy_search when only the option set is wanted. The Brand dimension is effectively Chewy's brand directory for the requested listing: each brand option carries its product count and, where Chewy publishes one, its own chewy.com/brands/- landing-page slug in seo_hvf_slug. Exactly one of group_id or q is required. Every facets[].value paired with one of that facet's options[].value is a ready-to-use filter key:value pair for this endpoint, chewy_category, and chewy_search alike; passing filter here narrows the listing first, so the returned counts describe the already-narrowed result set. A group_id Chewy does not recognize returns a 404 rather than an empty option set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search keywords to return refinement options for, e.g. \
filterNoRepeatable, up to 10. Each value is \
group_idNoChewy's numeric category id, e.g. \

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.4/5.0
Behavior5/5

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

Clearly states the return data (refinement options with product counts), the relationship to chewy_category and chewy_search, and the behavior of invalid group_id (returns 404). No ambiguity about what happens when the tool is called. There is no statement of side effects, but for a read-only facets endpoint, that omission is not material.

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 long but information-dense, with zero repetition or filler. It reads logically from use case, to available modes, to filtering semantics, to caveats. All content earns its place – no markdown, no fluff, no duplicated schema information.

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?

Names four sibling endpoints tied to the same domain (chewy_*), explains the trade-off between this and search, warns about pagination and the special semantics of this endpoint. Missing: what happens for empty or failed root list calls (falls back to search product), which is background context not a parameter detail.

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?

The endpoint description states that at least one of group_id or q is required staring from Chewy API v2 and that they are mutually exclusive. However, the property descriptions read 'Filter by Chewy category id' and 'Search query' – they do not explain that exactly one must be provided, which is a requirement the description itself sets. An agent reading the schema could plausibly omit both fields, or send both. The description also doesn't say what v is or what it does.

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 clearly states the purpose: to return facets/refinement options for Chewy searches, explicitly excluding product data. It also explicitly names the alternative to chewy_facets for when refinement options are not what the user wants.

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 explains the primary purpose (returning facets) and implicitly differentiates from a hypothetical product-search tool, but does not detail when to choose this tool over related sibling tools like product search within the same domain. It lacks explicit parameter guidance (e.g., when to use group_id vs. q), relying on schema to communicate requirement. Still, the core usage — supply either a category ID or a search query — is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools