Trello MCP Server

Delete Checklist

delete_checklist

Delete a checklist permanently from a Trello card by providing its checklist ID. Removes unwanted checklists to keep your card organized.

Instructions

Permanently delete a checklist from 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": {
      "checklistId": "<checklistId>"
    },
    "name": "delete_checklist"
  }
}

Input Schema

Name	Required	Description	Default
`checklistId`	Yes	The ID of the checklist to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses irreversibility via 'Permanently delete', which is a key destructive signal, but it omits consequential side effects such as the removal of all checklist items, which would be important for an agent invoking a destructive operation.

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 a single, information-dense sentence with no wasted words. Permanence, the action, and the object are all front-loaded, making it highly scannable for an agent.

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?

Although the tool is structurally simple (one param, no annotations, no output schema), the description is missing critical context for a destructive operation: it does not mention cascading effects (such as deleting the checklist's items) or any permission/precondition requirements. The bare statement leaves an agent with limited ability to anticipate the full impact.

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?

The input schema fully documents the single parameter checklistId with a clear description. The tool description adds no additional parameter-level meaning, so the baseline of 3 applies since schema coverage is 100%.

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: 'Permanently delete a checklist from a card.' It clearly targets the whole checklist entity, distinguishing it from sibling tools like delete_checklist_item, and provides the card context that anchors the operation.

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?

The description gives no explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The distinction from delete_checklist_item is only implied by the name and the word 'checklist', not stated.

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

Deploy Server