Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chewy_category

Browse a Chewy category listing by group_id to retrieve product details, ratings, and filtering facets for that category.

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. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / filter / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "byRelevance",
+  "byNewest",
+  "byPopularity",
+  "byLowestPrice",
+  "byHighestPrice",
+  "byRating",
+  "byRatingCount"
+]
  2. 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"
+}
  3. Addedv1.16.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses the 404 behavior for unrecognized group_ids, the response contents (price, autoship price/discount, stock, rating, images, facets, breadcrumbs), the optional include_content behavior with no extra upstream call, and sort/filter mechanics.

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 dense but well-organized; every sentence earns its place. It front-loads the core purpose and response summary before diving into group_id semantics, error behavior, filter/sort mechanics, and include_content details, with no fluff.

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 the absence of an output schema and annotations, the description is remarkably complete. It covers the return fields, pagination via the page parameter, error handling for invalid group_ids, and the follow-up usage pattern for facets and filters, giving an agent everything needed to call and use the tool correctly.

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?

Despite 100% schema coverage, the description adds substantial meaning: it defines group_id with a concrete URL example, explains that breadcrumbs[].group_id and facets[].options[].value are reusable group_ids for follow-up calls, specifies that any facets[].value paired with one of its options[].value is a valid filter key:value pair, and clarifies that include_content is omitted entirely when not requested.

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 clear verb+resource: 'Browse a Chewy category listing' and specifies the response contents (36 products, product grid fields, facets, breadcrumbs). It distinguishes itself from search by noting 'A keyword search carries none of this content, so it is a category-only addition.'

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 gives a clear use case: browsing a category and discovering the taxonomy via breadcrumbs and facets. It compares against keyword search, stating search lacks the category content, but it does not explicitly name sibling tools like chewy_search or chewy_categories or provide formal when-not conditions.

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