SiteCheck Crypto & Finance

leboncoin.fr classified-ads search: result totals and 35

finance_leboncoin

Read-only

leboncoin.fr classified-ads search (all of France): result totals (all / private / pro) and 35 ads per page with ad id, title, price (EUR), category, city, zip, department, region, latitude/longitude, seller name and type, first publication date, photo count and first photo, boosted flag and ad link. From leboncoin.fr via a stealth proxy. Takes about 20 s; allow a 30 s timeout. Related tools on this server, for a different need: finance_bstock when you need B-Stock wholesale liquidation auctions: total live lots; finance_coingecko when you need CoinGecko spot prices for up to 10 coins in one currency. Price: $0.03 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": "finance_leboncoin"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	Result page 1-100 (default 1)
`query`	Yes	Search words in French, e.g. velo, iphone 15, canapé

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds substantial context: access via a stealth proxy, ~20 s runtime with a 30 s timeout target, 35 ads per page cap, and the x402 payment model ($0.03 USDC, failed calls not charged). That cost and latency disclosure is exactly what an agent needs before invoking.

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 and scope are front-loaded in the first clause, followed by returned fields, operational facts, alternatives, and pricing. The long field enumeration is somewhat redundant given an output schema exists, but it is a single readable sentence and nothing is buried.

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 paid, proxied, slow scrape tool, the definition covers scope, latency, timeout budget, result shape, page limits, alternatives, and cost/charging policy — everything needed to call it correctly. The output schema handles return-value detail, so no further explanation is required.

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%: 'query' (French search words) and 'page' (1-100, default 1) are already documented in the schema. The description adds only the geographic scope ('all of France'), which is not parameter-specific, so it contributes nothing beyond the structured fields. 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?

Opens with a specific verb+resource ('leboncoin.fr classified-ads search') plus scope ('all of France'), then enumerates the returned data (totals, 35 ads, price in EUR, location, seller). An agent can distinguish it from the crypto/wholesale finance siblings without opening a 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 the agent elsewhere: 'finance_bstock when you need B-Stock wholesale liquidation auctions' and 'finance_coingecko when you need CoinGecko spot prices,' framed as 'for a different need.' Usage is clear, though it offers no when-not-to-use conditions for this tool itself (e.g., query language limits beyond 'French').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Crypto & Finance 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?