Skip to main content
Glama

delete_board

Destructive

Permanently deletes a Trello board and all its lists and cards; cannot be undone, so close it instead if you may need it later.

Instructions

PERMANENTLY delete a board with all its lists and cards. Cannot be undone; prefer update_board 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": {
      "boardId": "<boardId>"
    },
    "name": "delete_board"
  }
}

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.
boardIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the description's real contribution is the cascade detail — child lists and cards are destroyed too — plus explicit irreversibility. It does not cover permission requirements or what the call returns, which is why this is not a 5.

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 sentences with zero filler, and the most consequential fact ("PERMANENTLY") is front-loaded before the scope and the safer alternative.

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 destructive mutation with no output schema, the description covers the two things an agent must know: what is destroyed and that it is irreversible. Missing only permission/authorization expectations, which is a minor gap given the annotations already flag destructiveness.

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-schema, but boardId has no description anywhere. The tool description never mentions either parameter, so it does nothing to close the gap for the required boardId.

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 names a specific verb and resource ("PERMANENTLY delete a board") and defines the cascade scope ("with all its lists and cards"). The contrast with update_board makes it distinguishable from the closest sibling at a glance.

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?

It explicitly routes the agent to an alternative ("prefer update_board with closed=true") and states the condition that selects it: irreversible destruction versus archiving. That is both a when-to-use and a when-not-to-use rule in one clause.

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