Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chewy_search

Search Chewy by keyword to fetch one page of normalized product listings with prices, Autoship discounts, stock, ratings, images, and facets.

Instructions

Search Chewy by keyword. Returns one page of a Chewy keyword search's normalized 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

TableJSON 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

A4.3/5.0
Behavior4/5

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

Annotations are not provided; the description carries the full burden. It clearly states the return includes a normalized product listing and facets, and explains the redirection behavior for category-matching queries. However, it does not disclose rate limits, auth needs, or potential side effects, but for a search tool these are less critical. The description does not contradict annotations.

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 a single well-structured paragraph, front-loaded with the core purpose and return format. It is somewhat long but each clause adds useful information (redirection, filter guidance). No wasted words, though it could be split into two sentences for readability.

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 that the tool has 4 parameters (all documented in schema), lacks an output schema, but has a rich description covering return fields and filter semantics, the description is quite complete. It would benefit from mentioning pagination limits or page behavior beyond the schema, but the page parameter is documented and 36 products per page is given in the schema. Overall adequate.

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?

Schema coverage is 100%, so the schema already documents q, page, sort, and filter. The description adds some nuance: it explains that q is free-text keywords and gives an example, and it explains how filter keys pair with facet values from prior responses. This goes beyond the schema's basic descriptions, but not heavily.

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 tool searches Chewy by keyword and returns a normalized product listing with facets. It specifies the exact verb and resource ('Search Chewy by keyword'), and mentions the return format includes price, autoship price, stock, rating, images, and facets. This differentiates it from other tools like chewy_product or chewy_categories.

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: for keyword searches, and notes that generic queries matching Chewy's categories are redirected to the category listing, transparently. It does not offer a direct comparison to sibling tools (like chewy_categories), but the behavior is well-defined and the conditions for redirection are clearly stated.

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