Skip to main content
Glama

remove_label

Detach a label from a Trello card while keeping the label available on the board.

Instructions

Detach a label from a card (the label itself stays on 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": {
      "cardId": "<cardId>",
      "labelId": "<labelId>"
    },
    "name": "remove_label"
  }
}

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
labelIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations declare destructiveHint=false, and the description reinforces this with the concrete consequence that the label itself stays on the board — genuinely useful context that tells the agent this only severs the association. It does not cover permission requirements or what the response reports, so it is not fully comprehensive.

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 front-loaded sentence with the core action first and the clarifying caveat in parentheses. No filler, nothing that could be cut.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small three-parameter mutation the description covers the essential semantics of the operation and its non-destructive nature. It leaves out ID provenance and post-call state/permission expectations, which matters given no output schema exists.

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 33% (just the lang parameter), and the description says nothing about cardId or the two-thirds of parameters left undocumented. It does not clarify where these IDs come from or whether labelId is a board-level label id, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Detach a label from a card") and the parenthetical clarifies the scope of the operation, so an agent can tell it apart from add_label or a label-deleting operation. It stops short of naming a sibling explicitly, so not a 5.

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?

Usage is only implied: an agent can infer this is the inverse of add_label and applies to cards that already carry the label. There is no explicit when-to-use statement, no guidance on obtaining cardId/labelId, and no mention of what to do if the label is not on the card.

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