SiteCheck Shop & Social

Faire wholesale marketplace category listing: product

ecommerce_faire

Read-only

Faire wholesale marketplace category listing (logged-out view): product token, name, brand name and token, suggested retail price (USD), case quantity, stock units, brand rating and review count, new / bestseller / promoted flags, brand's country, image and product link. Wholesale prices need a retailer login and are not included. From faire.com via a residential proxy. Related tools on this server, for a different need: ecommerce_revzilla when you need RevZilla motorcycle gear and parts in a category: product; ecommerce_aliexpress when you need AliExpress product search from the public search page. Price: $0.02 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_faire"
  }
}

Input Schema

Name	Required	Description	Default
`category`	Yes	Faire category name as in faire.com/category/<name>, e.g. Home Decor, Food & Drink, Women, Beauty & Wellness, Jewelry, Kids & Baby, Pets

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses that data comes via a residential proxy, that wholesale pricing is gated behind retailer login and thus absent, and the exact cost model ($0.02 USDC per successful call via x402 on Base/Solana/Arc, failures uncharged). These are exactly the behavioral facts an agent cannot infer from annotations and that affect whether it should call at all.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, which is good, but the opening sentence is a long comma-spliced inventory of returned fields that duplicates what the output schema already declares. The proxy, pricing, and sibling-tool sentences all earn their place; the field enumeration does not.

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, the description does not need to explain return shape, and it covers the gaps that matter: auth-gated wholesale prices, proxy sourcing, and pay-per-call cost. Nothing critical about calling the tool correctly is missing, though it never states pagination or result-count limits for a listing endpoint.

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% and the single category parameter is documented with concrete examples (Home Decor, Food & Drink, Women, etc.). The description adds nothing about the parameter itself beyond the word 'category' in the title phrase, so it sits at the baseline for a fully documented single-param schema.

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 identifies the resource and scope precisely (Faire category listing, logged-out view) and even enumerates the fields produced, so an agent knows exactly what comes back. It also names two sibling tools (ecommerce_revzilla, ecommerce_aliexpress) and the different needs they serve. The verb is implicit in the noun phrase 'category listing' rather than stated outright, which keeps it just short of a 5.

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 clear context for use: logged-out public view, wholesale prices require a retailer login and are therefore unavailable here. The 'Related tools on this server, for a different need' sentence routes the agent to RevZilla and AliExpress alternatives with their distinguishing domains. There is no explicit 'do not use this when...' exclusion, so it falls short of a 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?