Skip to main content
Glama

Crawlora MCP

chewy_facets

Read-only

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. Returns no products, so it 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 that 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 chewy_facets, chewy_category, and chewy_search alike; passing filter here narrows the listing first, so the returned counts describe the already-narrowed result set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoOptional. Free-text search keywords to return the refinement options for, e.g. "salmon dog food". Exactly one of group_id or q is required.
filterNoOptional, repeatable, up to 10. Each value is "key:value" -- a facets[].value paired with one of that facet's options[].value, e.g. "brand_facet:ACANA". Narrows the listing first, so the returned option counts describe the already-narrowed result set.
group_idNoOptional. Chewy's own numeric category id -- the trailing id segment of a chewy.com/b/<slug>-<id> browse URL, e.g. 294 for /b/dry-food-294. Exactly one of group_id or q is required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only and open-world safety, lowering the burden. The description adds real behavioral context: it returns no products so it is a smaller call, returned counts describe the already-narrowed result set, and brand options may carry a seo_hvf_slug. It does not discuss rate limits or pagination, so not a 5.

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 with the core purpose and routing, then details. It is somewhat long and repeats the filter-narrows-listing behavior already stated in the schema, but every sentence is relevant and no critical content is buried.

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 three-parameter, no-required-input facet tool with an output schema and read-only annotations, the description is complete: it covers purpose, when-to-use, filter semantics, and how returned counts behave. Output details can be left to the output schema.

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 baseline is 3. The description adds meaning beyond the schema by explaining that any facets[].value + options[].value pair is a ready-to-use key:value filter reusable across chewy_facets, chewy_category, and chewy_search, and reiterates the exactly-one-of group_id/q constraint.

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: returns the full set of refinement options (facets) for a Chewy category or keyword search, and explicitly contrasts itself with siblings by noting it 'Returns no products, so it is a much smaller call than chewy_category/chewy_search'. An agent can distinguish it from the sibling search tools without opening any schema.

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?

Explicitly names the condition for choosing this tool ('when only the option set is wanted') and the alternatives (chewy_category/chewy_search). Also explains that 'filter here narrows the listing first', giving the agent a clear decision rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources