SiteCheck Shop & Social

RevZilla motorcycle gear and parts in a category: product

ecommerce_revzilla

Read-only

RevZilla motorcycle gear and parts in a category (e.g. motorcycle-helmets, motorcycle-jackets, motorcycle-tires): product name, brand, price (USD), in-stock flag, rating, review count, badge (top rated, new...), free-shipping flag, image and link; 96 per page (page 1 to 20), plus the category's product count. From revzilla.com's public category pages via a residential proxy. Related tools on this server, for a different need: ecommerce_faire when you need Faire wholesale marketplace category listing: product; ecommerce_aliexpress when you need AliExpress product search 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": {
      "category": "<category>"
    },
    "name": "ecommerce_revzilla"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Results page 1 to 20 (default 1)
`category`	Yes	Category slug as in revzilla.com/<slug>, e.g. motorcycle-helmets, motorcycle-jackets, motorcycle-gloves

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations by disclosing the data acquisition path (revzilla.com public category pages via residential proxy), the pagination ceiling (96 per page, pages 1–20), and a full billing model: $0.002 USDC per successful call via x402 on Base, Solana or Arc, with failed calls not charged. Cost and failure-charging behavior are exactly the traits an agent cannot infer from annotations or schema.

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?

Purpose is front-loaded and every clause carries information — fields, pagination, source, alternatives, price — with no filler. The semicolon-chained run-on makes it denser than ideal to scan, but nothing is expendable.

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?

For a two-parameter, read-only listing tool with an output schema, everything an agent needs is present: the resource, the field set, pagination limits, cost and payment rail, failure billing, and sibling routing. No open question remains that would cause a misinvocation.

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 already 100%, so the baseline is 3; the description adds genuinely new semantics by stating the page size is 96 items, which the schema omits and which materially affects how many calls a task needs. Example category slugs overlap the schema's own description, but the resulting-page-size detail is additive.

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?

Names the specific resource (RevZilla motorcycle gear and parts in a category) and enumerates exactly what each record contains: product name, brand, price in USD, stock flag, rating, review count, badge, shipping flag, image, link. It also states the page size and that the category's product count is included, so an agent knows precisely what a call yields without opening the output 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?

Explicitly routes away to two named siblings with their conditions (ecommerce_faire for Faire wholesale categories, ecommerce_aliexpress for AliExpress search), which is real when-to-use guidance. It stops short of stating exclusions for this tool itself — e.g. that it is category browsing only and not keyword search on RevZilla — so the boundary is implied rather than fully closed.

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?