Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chewy_category

Fetch a Chewy category page by group_id: 36 products with price, rating, stock, images, and filters. Use breadcrumb and facet IDs to explore the category taxonomy or refine results.

Instructions

Browse a Chewy category listing. Returns one page (36 products) of a Chewy category/browse listing's product grid (price, autoship price/discount, stock, rating, images), plus embedded facets and breadcrumbs. group_id is Chewy's own numeric category id -- the trailing id segment of a chewy.com/b/- browse URL, e.g. 294 for /b/dry-food-294. Every breadcrumbs[].group_id and facets[].options[].value in a response is a ready-to-use group_id for a follow-up call, so a caller can discover the full category taxonomy starting from a known category. A group_id Chewy does not recognize returns a 404 rather than an unfiltered listing. sort and filter narrow/reorder the listing; every facets[].value paired with one of that facet's options[].value from any prior response is a valid filter key:value pair (e.g. brand, breed size, flavor, price range, customer rating -- whichever facets that category exposes). Set include_content to also return the category's curated editorial content -- Chewy's own FAQ question/answer pairs, the rich category description, and the SEO page title and meta description; it costs no extra upstream call and is omitted entirely when not requested. A keyword search carries none of this content, so it is a category-only addition.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 36 products per page (default 1)
sortNoSort order. One of byRelevance, byNewest, byPopularity, byLowestPrice, byHighestPrice, byRating, byRatingCount. Defaults to Chewy's own relevance ordering when omitted.
filterNoRepeatable, up to 10. Each value is \
group_idYesChewy's numeric category id, e.g. \
include_contentNoAlso return the category's curated editorial content -- Chewy's own FAQ question/answer pairs, the rich category description, and the SEO page title/meta description. Costs no extra upstream call. Omitted entirely when false (the default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.2
    • addedInput schema / properties / include_content
      Added value: +{
+  "description": "Also return the category's curated editorial content -- Chewy's own FAQ question/answer pairs, the rich category description, and the SEO page title/meta description. Costs no extra upstream call. Omitted entirely when false (the default).",
+  "type": "boolean"
+}
  2. Addedv1.16.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses pagination behavior (36 products per page), the 404 behavior for invalid group_ids, the fact that include_content costs no extra upstream call, and that content is omitted entirely when not requested. It also explains the filter key:value pairing semantics. The only minor gap is not describing the exact response envelope or error format beyond 404, but the disclosed behaviors are substantial and useful.

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?

The description is dense but well-organized, front-loading the core purpose and return contents before diving into parameter semantics. Every sentence adds information: pagination, group_id derivation, facet reuse, 404 behavior, filter pairing, and include_content. It is longer than average, but the length is justified by the complexity of the tool's parameters and the need to explain Chewy-specific concepts. A slight trim of the filter example list could improve it, but it remains efficient.

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?

Given the tool's complexity (5 parameters, no output schema, no annotations), the description covers the essential operational knowledge: what group_id is, how to obtain it, how filters work, what include_content does, and the 404 edge case. It does not describe the exact structure of the response beyond listing product fields and facets, but with no output schema, a bit more detail on the response envelope would be ideal. Still, the description is remarkably complete for an agent to call this tool correctly.

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 description coverage is 100%, so the baseline is 3. The description adds significant meaning beyond the schema: it explains how group_id relates to a Chewy URL, how facets[].options[].value can be reused as group_id, how filter values pair with facet options, and what include_content returns. This goes well beyond the schema's terse parameter descriptions, though the filter parameter's schema description appears truncated, and the description partially compensates for that.

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 a specific verb and resource: 'Browse a Chewy category listing.' It clearly states what is returned (one page of 36 products with price, autoship, stock, rating, images, facets, breadcrumbs) and distinguishes itself from sibling tools like chewy_search and chewy_categories by focusing on category/browse listings. The group_id explanation with a concrete URL example removes ambiguity about the required parameter.

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?

The description explicitly explains when to use this tool: to browse a category listing, and it contrasts with keyword search, noting that keyword search carries none of the editorial content. It also explains how to discover group_ids from breadcrumbs and facets, and warns that an unrecognized group_id returns a 404 rather than an unfiltered listing. This gives an agent clear decision rules for selecting this tool over alternatives.

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