Skip to main content
Glama

delete_card

Destructive

Permanently deletes a Trello card by ID; use only when removal is intended, as the action cannot be undone.

Instructions

Permanently delete a card. This cannot be undone; prefer update_card with closed=true.

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

NameRequiredDescriptionDefault
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
cardIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the irreversibility warning in the description is largely reinforcing structured data rather than adding new behavior. The description does not mention side effects such as what happens to a deleted card's attachments, comments, or checklist items, nor any cascade or permission requirements.

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, zero filler, with the destructive nature front-loaded ahead of the safer alternative. Every clause earns its place.

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 single-resource destructive tool with full annotation coverage and no output schema, the definition gives purpose, risk, and an alternative. The only real gap is the undocumented cardId and the absence of any note on cascade effects.

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?

Schema description coverage is only 50%: the lang parameter is documented in the schema, but cardId is bare. The description says nothing about either parameter or what identifier form cardId expects, so it does not compensate for the coverage gap.

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?

"Permanently delete a card" states a specific verb and resource, and the qualifier "Permanently" immediately separates it from the soft, reversible removal implied by siblings like update_card or archive_list. An agent can distinguish it from the other delete_* and update_card tools without opening any schema.

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?

It explicitly routes the agent to an alternative: "prefer update_card with closed=true," which is a clear when-to-use-this-instead signal. It stops short of stating when deletion is actually appropriate (e.g. card created in error) or any preconditions such as permissions, so it is clear but not exhaustive.

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