Skip to main content
Glama
rachid598

leboncoin-seller-mcp

by rachid598

Prepare a Leboncoin listing

prepare_listing

Turns photo observations and item facts into a local ad draft with comparable pricing, category, title, and description—nothing published. Works offline with research set to false.

Instructions

The main entry point. Give it what you can actually SEE in the photos plus the photo paths, and it creates a local draft: searches comparable ads, computes a price from their asking prices, resolves the category, and writes a title and description from the facts you supplied. Nothing is sent to Leboncoin and nothing is published. The draft lives on this machine. Show the result to the user, apply their corrections with update_listing_draft, then validate_listing. Set research: false to build the draft without touching the network at all - useful when Leboncoin is blocking and you still want a draft the user can copy in by hand.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoSize or dimensions as printed or measured.
brandNoBrand exactly as it appears on the item. Leave empty if you cannot read it - do not guess.
colorNoMain colour, in French where possible.
modelNoModel or product name, e.g. "Exos X18", "iPhone 13".
notesNoAnything else worth telling a buyer, e.g. "facture et boîte d'origine".
priceNoSet the price yourself and skip the estimate.
titleNoOverride the generated title. Leboncoin caps titles at 50 characters.
photosNoPhotos to attach. They are COPIED into the draft; your originals are never moved or modified.
countryNoLeboncoin site to use (fr). Defaults to the server's configured site.
defectsNoEvery visible flaw: scratches, dents, missing parts. These are always kept in the description.
queriesNoExtra search phrasings for the comparable hunt.
workingNoWhether the item is known to work. Omit if you do not know - do not assume.
capacityNoStorage, volume or power, e.g. "8 To", "128 Go", "1500 W".
categoryNoFree-text category guess in French, e.g. "disque dur", "canapé".
currencyNo
locationNoWhere the item is. Leboncoin requires this before publishing.
materialNoMaterial, e.g. "chêne massif", "cuir".
researchNoSet false to create the draft offline. Default true.
shippingNoWhether you offer delivery, and how.
conditionNoCondition. Pick the one the photos actually support, not the flattering one.
referenceNoReference / SKU / part number if visible on a label or the item.
categoryIdNoNumeric category id from find_category. Must be a leaf category.
descriptionNoOverride the generated description.
Behavior5/5

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

Adds critical behavioral context beyond annotations: 'Nothing is sent to Leboncoin and nothing is published. The draft lives on this machine.' Also explains the offline mode with research:false. This aligns with annotations (openWorldHint=true, destructiveHint=false) and provides additional safety reassurance.

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 two paragraphs, front-loaded with the primary purpose, and uses bold for key phrases like 'Nothing is sent' and 'research: false'. Every sentence adds value, but the flow is a bit dense; however, it remains readable and structured well.

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?

Given the complexity (23 params, nested objects, no output schema), the description provides a complete overview of what the tool does from start to finish, including the workflow and offline option. It fully addresses the agent's need to understand the tool's behavior and role in the listing process.

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 96%, so the schema already documents parameters thoroughly. The tool description adds minimal parameter-specific guidance beyond what's in the schema (e.g., research:false, price skip). It does not compensate for any gaps but doesn't need to, given high coverage; baseline 3 is appropriate.

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 the tool's role as 'The main entry point' for creating a listing draft, detailing specific actions (searches comparables, computes price, resolves category, writes title/description). It distinguishes from sibling tools like update_listing_draft and validate_listing by describing the full pipeline.

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?

Explicitly outlines the workflow: 'Show the result to the user, apply their corrections with update_listing_draft, then validate_listing.' Also gives a specific use case for setting research:false 'when Leboncoin is blocking and you still want a draft the user can copy in by hand.' This provides clear when-to-use and alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rachid598/mcplebon'

If you have feedback or need assistance with the MCP directory API, please join our Discord server