SiteCheck Shop & Social

Zazzle product search from the public search page: product

ecommerce_zazzle

Read-only

Zazzle (US) product search from the public search page: product ID, title, product type, price and current sale price in USD, discount %, promo label, all-time order count, store name and handle, image and product URL; 60 products per page plus the total number of matching products and pages. Prices are Zazzle's default-configuration prices at the time of the call. Related tools on this server, for a different need: ecommerce_aliexpress when you need AliExpress product search from the public search page; ecommerce_petco when you need Petco.com product search read from the public search page. 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": {
      "q": "<q>"
    },
    "name": "ecommerce_zazzle"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search words, e.g. mug, tote bag, wedding invitation (required, 2-80 chars)
`page`	No	Page number 1 to 16 (default 1)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses page size (60 products), that the total match/page count is returned, that prices reflect default configurations at call time, and the exact billing model ($0.002 USDC per successful call via x402, failures not charged). Cost and data-freshness semantics are exactly the kind of context annotations cannot carry.

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 result fields, pagination, price semantics, and pricing are front-loaded before the alternative-tool routing, and every sentence carries information. The dense semicolon-delimited field list and the repetitive 'when you need ... from the public search page' phrasing in the sibling sentences cost some tightness.

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?

With an output schema present, return-value detail need not be explained, and the description still covers scope, pagination, and cost. The only small gap is behavior beyond the 16-page cap, which the description does not address.

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 description coverage is 100%, with q (2-80 chars, examples) and page (1-16, default 1) fully documented in the schema. The description adds the page-size context (60 products per page) but no additional syntax or query-shaping guidance, so the baseline 3 applies.

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?

States a specific verb+resource (product search) on a named site and enumerates exactly what fields are returned (title, product type, price, sale price, discount %, promo label, order count, store handle, URLs). It also explicitly distinguishes itself from ecommerce_aliexpress and ecommerce_petco, so an agent can route without opening schemas.

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 related-tools sentence gives clear routing context: use this for Zazzle, use ecommerce_aliexpress for AliExpress, use ecommerce_petco for Petco. There is no explicit when-not-to-use condition (e.g., for non-US Zazzle or for product-detail lookups), so it stops short of a full 5.

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?