leboncoin-seller-mcp

Delete a local draft

delete_draft

Destructive

Delete a local draft and its associated photos without affecting any published Leboncoin ad. Use force: true only when the draft was published or its state is unknown.

Instructions

Removes a local draft and its copied photos. Does not touch anything on Leboncoin - a published ad stays published. Drafts that were published, or whose publish ended in an unknown state, need force: true, because that local record is the only trace linking a live ad back to this draft.

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": {
      "draftId": "<draftId>"
    },
    "name": "delete_draft"
  }
}

Input Schema

Name	Required	Description	Default
`force`	No	Delete even if the draft was published or ended in an unknown state.
`draftId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 22, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint, readOnlyHint), the description discloses additional behavioral details: it removes copied photos, does not affect Leboncoin, and explains the rationale for force deletion (local record is the only trace linking to live ad). This adds valuable context that the annotations do not cover.

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 concise (two sentences) and well-structured, with bold for the key point. It front-loads the main action and then explains the exception. No unnecessary words or redundancy.

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 delete operation, the description covers the primary action, its scope, and the special condition for force. It lacks an explicit statement about the return value or irreversibility, but the destructiveHint covers the latter. Given the simplicity of the tool and no output schema, this is sufficient, though slightly more detail about success/error behavior would improve completeness.

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

Parameters4/5

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

Schema coverage is 50% (only `force` has a description). The description expands on `force` by explaining the reasoning behind needing it ('the local record is the only trace'), which goes beyond the schema's brief line. For `draftId`, it provides no additional meaning, but the name makes it clear. Given low coverage, this compensation is adequate.

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 verb ('Removes') and resource ('a local draft and its copied photos'), and explicitly distinguishes its scope from online content ('Does not touch anything on Leboncoin'). It is specific and distinct from sibling tools, which focus on other draft operations like get_draft, list_drafts, or update_draft.

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?

The description provides explicit guidance on when to use the `force: true` flag (for published drafts or unknown publish states) and clarifies that it does not affect published ads. While it doesn't mention alternative tools directly, the condition for `force` serves as a usage guideline for edge cases.

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