Trello MCP Server

Delete Board

delete_board

Permanently delete a Trello board and all its lists, cards, and data. Use when you need to remove an entire board irreversibly.

Instructions

Permanently delete a Trello board. WARNING: This is irreversible — all lists, cards, and data on the board will be lost.

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": {
      "boardId": "<boardId>"
    },
    "name": "delete_board"
  }
}

Input Schema

Name	Required	Description	Default
`boardId`	Yes	The ID of the board to permanently delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description must carry the behavioral disclosure burden. It does this well by warning that deletion is irreversible and that all lists, cards, and data will be lost. This goes beyond the schema and informs the agent of serious side effects.

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 two sentences with no wasted words. The critical warning about irreversibility is placed front and center, making it immediately salient to the agent.

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 main operational facts: what it deletes, permanence, and data loss. It doesn't mention return values or error conditions, but given the tool's simplicity and the schema covering the sole parameter, this is a minor gap rather than a critical omission.

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%, so the parameter 'boardId' is already fully documented. The description does not add additional parameter-level detail beyond the schema, which is acceptable given the baseline of 3.

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 action and resource: 'Permanently delete a Trello board.' This clearly distinguishes it from sibling tools like delete_card, delete_comment, or delete_webhook, and adds the crucial adverb 'permanently' to clarify scope.

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

Usage Guidelines3/5

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

The description makes the tool's purpose obvious, but it does not explicitly say when to use it versus alternatives or provide exclusions. Usage is implied rather than stated with alternative routing or conditions.

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

Deploy Server