lbc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LBC_PROXY | No | Proxy to use, e.g. http://user:password@host:port. | |
| LBC_EXPORT_DIR | No | Directory for CSV/JSON exports. | Téléchargements\leboncoin |
| LBC_IMPERSONATE | No | Browser whose TLS fingerprint lbc imitates. Can be chrome, edge, safari, safari_ios, firefox, etc. | chrome_android |
| LBC_MIN_INTERVAL | No | Minimum number of seconds between two requests to Leboncoin. | 2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_adsA | Recherche des annonces sur Leboncoin. Renvoie les totaux du site, des statistiques de prix sur les annonces recuperees et, pour chacune : id, titre, prix, date, lieu, categorie, URL et attributs utiles (etat, kilometrage, surface...). next_page indique la page a demander pour continuer. Pour le detail d'une annonce (description, photos, vendeur), utiliser get_ad. |
| get_adA | Detail complet d'une annonce : description, photos, tous les attributs, coordonnees, nombre de favoris et identifiant du vendeur (seller_id). |
| get_sellerA | Profil d'un vendeur : anciennete, note sur 5 et nombre d'avis, taux et delai de reponse, nombre d'annonces en ligne, et pour un professionnel sa boutique (SIRET, adresse, site web). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: searching ads, retrieving ad details, and fetching seller profiles. There is no overlap or ambiguity between them.
All tools follow a consistent verb_noun pattern in snake_case: search_ads, get_ad, get_seller. This makes the API predictable and easy to navigate.
With only 3 tools, the set is minimal but well-scoped for read-only classifieds access. Each tool is necessary and none are redundant, fitting the typical 3-15 tool range.
The tools cover the core browsing workflow: search, ad details, and seller info. A minor gap is the lack of a direct way to list all ads from a specific seller, though this might be achievable via search parameters.