Skip to main content
Glama

add_label

Attach an existing label to a Trello card using card and label IDs to categorize and organize cards.

Instructions

Attach an existing label to 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": {
      "cardId": "<cardId>",
      "labelId": "<labelId>"
    },
    "name": "add_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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety is partly covered. The description adds nothing beyond that: it does not say whether attaching twice is idempotent, what happens if the label is already on the card, whether permissions or board-membership are required, or whether the card's existing labels are affected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the action front-loaded and zero padding. It is efficient, though the terseness is achieved partly by omitting information rather than by tight writing.

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?

For a mutation tool with no output schema and three parameters (one undocumented in both schema and description), the description is too thin. It omits error behavior, idempotency, the required lang parameter, and what the call returns on success.

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 only 33% (only 'lang' is documented in the schema), so the description must compensate. It does clarify the roles of cardId and labelId by mapping 'label' and 'card' to them, but it says nothing about the required lang parameter or the identifier formats expected.

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?

States a specific verb and resource: 'Attach an existing label to a card.' The word 'existing' usefully rules out label creation, distinguishing it from create_label, though no sibling is named explicitly.

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?

There is no when-to-use guidance, no mention of the counterpart remove_label, and no explicit statement that a label must first be created via create_label. 'Existing' only weakly implies that prerequisite.

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