Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chewy_search

Search Chewy by keyword to get product listings with prices, autoship discounts, stock, ratings, and images. Filter and sort results using embedded facets and page through 36 items per page.

Instructions

Search Chewy by keyword. Returns one page of a Chewy keyword search's product listing (price, autoship price/discount, stock, rating, images), plus embedded facets. q is free-text search keywords, e.g. "salmon dog food". A generic query that strongly matches one of Chewy's own categories (e.g. "dog food", "cat litter", "leash") is transparently redirected to that category's listing, the same real results a chewy.com visitor would see -- source_url reflects the actual listing fetched. 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.

Input Schema

NameRequiredDescriptionDefault
qYesFree-text search keywords
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 \

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. Addedv1.16.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does well: it discloses the return shape (price, autoship price/discount, stock, rating, images, embedded facets), pagination behavior ('one page'), category-redirect behavior, and the meaning of source_url. It does not mention authentication, rate limits, or error behavior, which keeps it from 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?

The description is front-loaded with the core purpose and return type, then adds query, redirect, and filter details. It is mostly efficient, though there is slight redundancy between the opening 'Search Chewy by keyword' and the later 'q is free-text search keywords' explanation.

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?

For a 4-parameter tool with no output schema and no annotations, the description is fairly complete: it covers purpose, return fields, facets, pagination, redirect behavior, and filter semantics. It leaves out authentication needs, rate limits, and error handling, which are minor for a read-oriented search tool but still gaps.

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 the schema already documents the parameters. The description still adds meaning: it gives a concrete q example, explains that sort and filter narrow/reorder the listing, and clarifies the non-obvious filter key:value pairing using facets[].value and that facet's options[].value from a prior response. It does not add detail for page beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Search Chewy by keyword' and explains that it returns a product listing plus embedded facets. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as chewy_product, chewy_products, chewy_category, or chewy_suggest.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains mechanics and gives a query example, but it never states when to use this tool versus alternatives like chewy_category, chewy_product, or chewy_products. There are no explicit when-to-use or when-not-to-use guidelines, and the category-redirect behavior is described as a property rather than as guidance for tool selection.

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