mcp-lbc

search_ads

Search Leboncoin classified ads using filters for category, region, price, and sort order. Retrieve up to 10 results per query, limited to 10 requests per hour.

Instructions

Recherche des annonces Leboncoin avec filtres. Limité à 10 requêtes/heure (DataDome).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_ads"
  }
}

Input Schema

Name	Required	Default
`text`	No
`category`	No
`region`	No
`sort`	No	NEWEST
`limit`	No
`page`	No
`price_min`	No
`price_max`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 16, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The rate limit is disclosed, but no other behavioral traits like authentication needs, data freshness, or handling of missing results are mentioned. With no annotations, the description carries full burden and only covers one aspect.

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

Conciseness5/5

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

The description is extremely concise with two sentences, front-loading the purpose and rate limit constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters, an output schema, and a sibling tool, the description is insufficient. It lacks parameter guidance, pagination logic, and return value explanation, despite the output schema existing to mitigate completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description only says 'with filters' without explaining any of the 8 parameters (text, category, region, etc.), leaving the agent without meaning for the inputs.

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 clearly states it searches Leboncoin ads with filters, distinguishing it from sibling tool get_ad_detail which retrieves individual ad details.

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?

The description mentions a rate limit (10 requests/hour) but provides no guidance on when to use this tool versus the sibling, nor any prerequisites or limitations on filters.

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

Deploy Server