Trello MCP Server

delete_card

Permanently delete a Trello card by ID. This action is irreversible—archive the card first to keep a copy.

Instructions

⚠️ SUPPRIME DÉFINITIVEMENT une carte Trello (IRRÉVERSIBLE). Recommandation: archivez d'abord avec archive_card

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": {
      "cardId": "<cardId>"
    },
    "name": "delete_card"
  }
}

Input Schema

Name	Required	Description	Default
`cardId`	Yes	Parameter cardId (24 characters)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

No annotations exist, so the description carries the full burden of disclosure, and it delivers: it flags the operation as permanent and irreversible, the single most critical behavioral trait for a destructive tool, and adds a ⚠️ visual danger cue. There is no contradiction with any 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?

Two short sentences, both earning their place: the irreversible-danger warning is front-loaded first, and the mitigation advice (archive first) second. The emoji adds a quick visual signal without bulk; zero wasted words.

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 one-parameter destructive tool, the description covers the essential picture: what it does, that it is irreversible, and the safer sibling. Minor gaps remain — preconditions like board-close permissions, cascade effects on card content, and the response shape are unmentioned — but none are critical for correct invocation.

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 100% — cardId is already documented with its type and 24-character constraint. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource — 'SUPPRIME DÉFINITIVEMENT une carte Trello' (permanently deletes a Trello card) — and the (IRRÉVERSIBLE) marker distinguishes it from softer siblings like archive_card. An agent can tell exactly what the tool does and why it differs from alternatives.

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?

'Recommandation: archivez d'abord avec archive_card' explicitly names the alternative tool and directs the agent toward the safer default, implying delete is only for cases where permanent removal is intended. This is direct when-to-use routing with an explicit sibling reference.

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

Deploy Server