Trello MCP Server

Delete Label

delete_label

Permanently removes a Trello label from its board using the label ID. Use this to clean up unused or incorrect labels.

Instructions

Permanently delete a label from the board.

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": {
      "labelId": "<labelId>"
    },
    "name": "delete_label"
  }
}

Input Schema

Name	Required	Description	Default
`labelId`	Yes	The ID of the label to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description must bear the full behavioral burden. It discloses irreversibility with 'permanently delete', which is valuable, but it does not mention side effects, permissions, or response behavior.

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?

A single sentence with no filler. The key behavioral qualifier 'Permanently' is front-loaded, making the destructive nature clear immediately.

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 one-parameter destructive tool with no output schema, the description is nearly complete: it names the resource, confirms irreversibility, and the schema covers the only parameter. It could be more complete by describing consequences, but nothing necessary for calling is missing.

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%, so the schema already documents labelId. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb ('Permanently delete') and a specific resource ('a label from the board'), and is clearly distinguishable from siblings like get_label, update_label, and create_label by operation. It adds the 'permanently' nuance beyond the tool name.

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 implies the use case: call when a label needs to be permanently removed. However, it does not explicitly state when to prefer it over other label-related siblings or mention any exclusions, so guidance is only implied.

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

Deploy Server