SiteCheck Shop & Social

Back Market refurbished-product search on a country site

ecommerce_backmarket

Read-only

Back Market refurbished-product search on a country site (en-us, en-gb, fr-fr, de-de, es-es, it-it, ...): total hits and the first page of products with listing id, title, brand, model, category, condition grade, price and currency, new-device price, stock, review average and count, warranty months, colours, sales bucket, image and product link. From backmarket.com via a residential proxy. Takes about 20 s; allow a 45 s timeout. Related tools on this server, for a different need: ecommerce_aliexpress when you need AliExpress product search from the public search page; ecommerce_costco when you need Costco Canada product tracker: for 1-5 product IDs returns. 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": {
      "query": "<query>"
    },
    "name": "ecommerce_backmarket"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search words, e.g. iphone 14, macbook air, ps5
`locale`	No	Site locale: en-us (default), en-gb, fr-fr, de-de, es-es, it-it, nl-nl, en-au, ja-jp, ...

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses operational traits an agent cannot get elsewhere: a ~20 s runtime with a suggested 45 s timeout, access via a residential proxy, and pay-per-call pricing ($0.02 USDC via x402 on Base/Solana/Arc with failed calls uncharged). The only gap is no note on result volumne limits beyond 'first page'.

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, but the body is one long run-on sentence that dumps an eleven-field return list, then tacks on latency, siblings, and pricing. The field enumeration could be trimmed since an output schema exists, and the 'Related tools... for a different need' clause is awkwardly worded.

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?

Given an output schema exists, the description still covers the practical unknowns: expected latency and timeout budget, locale breadth, sourcing/proxy, and cost model. Nothing essential for a correct call is missing, though guidance on using this versus other retailer search tools is thin.

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%, so both query and locale are already documented. The description repeats the locale list (en-us, en-gb, fr-fr, de-de, es-es, it-it, ...) without adding format or validation meaning beyond the schema, so the baseline of 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 (search) and resource (Back Market refurbished products) scoped to a country site, and enumerates the returned fields (listing id, condition grade, price, warranty, etc.), so the agent knows exactly what it gets back. It also names sibling tools it is not, which separates it from the crowd of ecommerce_* search tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names two alternatives (ecommerce_aliexpress, ecommerce_costco) with the need each serves, so routing to other retailers is possible. However, it never states when this tool is the right choice versus the many other ecommerce search siblings, and gives no exclusions or prerequisites beyond the implied 'refurbished goods on Back Market'.

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?