SiteCheck Shop & Social

Costco Canada product tracker: for 1-5 product IDs returns

ecommerce_costco

Read-only

Costco Canada (costco.ca) product tracker: for 1-5 product IDs (the number at the end of a costco.ca product URL) returns name, brand, item number (SKU), price in CAD, availability (in stock / out of stock), shipping rate, rating and rating count, category path, description, image and URL, from each public product page's schema.org data. No keyword search; costco.com (US) is not reachable from the tool's network. Related tools on this server, for a different need: ecommerce_vestiairecollective when you need Vestiaire Collective listing tracker: for 1-10 listing IDs; 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": {
      "ids": "<ids>"
    },
    "name": "ecommerce_costco"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Comma-separated costco.ca product IDs or product URLs, 1 to 5, e.g. 100107807 (required)

Output Schema

Name	Required	Description	Default
`count`	No
`source`	No
`country`	No
`products`	No
`checkedAt`	No

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?

Beyond the readOnly and openWorld annotations, it discloses the data source (schema.org data on public product pages), pricing and payment mechanics, and that failed calls are not charged. These details materially affect invocation decisions and cost expectations.

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 information-dense and front-loads the core purpose, supported fields, exclusions, alternatives, and pricing. It is somewhat long and lists sibling tools verbosely, but nearly every clause contributes useful selection context.

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 one-parameter tracker with an output schema and annotations, the description covers scope, return contents, domain limitations, alternatives, and billing behavior. Nothing essential for correct selection or invocation appears to be missing.

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%, and the schema already documents comma-separated IDs/URLs with an example. The description adds minor interpretive value by clarifying that the ID is the number at the end of a costco.ca product URL, but most parameter meaning is already in the structured schema.

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/resource pair: a Costco Canada product tracker that takes 1-5 costco.ca product IDs and returns detailed product data. It also distinguishes itself from siblings by explicitly excluding keyword search and clarifying that costco.com US is not reachable.

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?

It clearly explains when this tool applies: product IDs from costco.ca, with no keyword search support and no US Costco access. It also names related alternative tools and the different needs they serve, so an agent can route away when appropriate.

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?