SiteCheck Shop & Social

Chewy item tracker: for 1-10 Chewy item IDs returns name

ecommerce_chewy_com

Read-only

Chewy (US) item tracker: for 1-10 Chewy item IDs (the number after /dp/ in a chewy.com URL) returns name, brand, price, strike-through price, Autoship price and discount, per-unit price, in-stock / discontinued flags, shipping timeframe, GTIN, rating and rating count, active promotions, size/flavor variants with their prices and stock, and key attributes. From the GraphQL API chewy.com's product pages use; no keyword search. Related tools on this server, for a different need: ecommerce_metalprices_com when you need latest precious-metal prices from MetalpriceAPI: USD per. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>"
    },
    "name": "ecommerce_chewy_com"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Comma-separated Chewy item IDs or chewy.com product URLs, 1 to 10, e.g. 323026 (required)

Output Schema

Name	Required	Description	Default
`count`	No
`items`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely useful context beyond that: the data comes from the GraphQL API behind chewy.com product pages, and each successful call costs $0.002 in USDC via x402 on Base/Solana/Arc with failed calls uncharged. The payment and provenance details are the kind of behavioral fact an agent cannot get from the annotations; only rate limits and any ID-format rejection behavior are absent.

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 core purpose and return fields are front-loaded in the first sentence, with sourcing, the keyword-search exclusion, and pricing following in a logical order. The aside about ecommerce_metalprices_com's precious-metal pricing is tangential filler that dilutes focus for a Chewy tool.

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?

An output schema exists, so the enumerated return fields are a bonus rather than a requirement. Combined with the read-only annotations, the /dp/ ID extraction hint, the cost model, and the explicit absence of keyword search, an agent has everything needed to invoke this correctly and predict the charge.

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% and there is a single parameter, so the baseline would be 3. The description still adds meaning by defining the item ID as the number after /dp/ in a chewy.com URL, which disambiguates what an agent should extract from a product link, going slightly beyond the schema's 'Chewy item IDs or chewy.com product URLs'.

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 states a specific verb and resource — a Chewy (US) item tracker that takes 1-10 item IDs and returns a named list of fields (name, brand, price, Autoship price, stock flags, GTIN, variants). It also draws a hard boundary with 'no keyword search', so an agent can tell it apart from search-style siblings like ecommerce_petco without opening the schema.

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?

It gives a clear when-to-use signal (lookup by item ID, resolved from a chewy.com /dp/ URL) and an explicit when-not ('no keyword search'). It names one alternative, ecommerce_metalprices_com, but that sibling serves an unrelated need, so it does not help the agent choose among the many ecommerce lookups on this server.

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

All SiteCheck Shop & Social tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?