leboncoin-seller-mcp

List listing drafts

list_drafts

Read-only

List local ad drafts, newest first, with status and headline. Filter by status to review or manage your unpublished Leboncoin listings before publishing.

Instructions

Lists local drafts, newest first, with their status and headline fields.

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": "list_drafts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`status`	No	Filter by status.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The readOnlyHint annotation already signals a safe read. The description adds useful behavioral detail beyond that: drafts are local, sorted newest first, and include status and headline fields. There is no contradiction with the annotation.

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 a single, focused sentence that front-loads the action and provides only relevant details. It avoids filler, redundancy, and unnecessary complexity.

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?

For a simple read-only listing tool with optional parameters and no output schema, the description covers the essential purpose, ordering, and returned fields. It would be more complete if it clarified default limit behavior and when to use this listing tool instead of related listing tools.

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

Parameters2/5

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

The description does not explain the limit or status parameters beyond what the schema already states. One parameter (limit) has no schema description and the description does not compensate by mentioning defaults, ordering with limit, or how filtering interacts with the returned fields.

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 'Lists local drafts, newest first, with their status and headline fields,' providing a specific verb, resource, and return scope. It distinguishes this from get_listing_draft and search_listings by focusing on the local draft list, ordering, and displayed fields.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives like search_listings, get_listing_draft, or my_listings. There are no use-case conditions, exclusions, or preferred scenarios, so the agent gets only minimal implied usage.

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