Trello MCP Server

trello_delete_card

Remove a Trello card by its ID to declutter boards and manage workflows. This tool permanently deletes specified cards from Trello boards.

Instructions

Delete a 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": {
      "card_id": "<card_id>"
    },
    "name": "trello_delete_card"
  }
}

Input Schema

Name	Required	Description	Default
`card_id`	Yes	The ID of the card

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 10, 2026

TDQS

C2.2/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states 'Delete', which is already clear from the name. It omits critical details like irreversibility, side effects on attachments/comments, or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely terse (3 words), but conciseness should not come at the expense of missing essential information. It fails to earn its place by providing no behavioral or usage context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations, output schema, and behavioral details, the description is insufficient for an agent to fully understand the tool's impact and proper use.

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 coverage is 100% as the only parameter 'card_id' has a description in the schema. The tool description adds no additional parameter context, achieving the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a card' is a direct tautology of the tool name 'trello_delete_card', adding no new information about the specific resource or action beyond the name itself.

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?

No guidance is provided on when to use this tool versus siblings like trello_archive_list or trello_update_card, nor any context on prerequisites or alternatives.

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