Skip to main content
Glama

Set, add or remove card labels

kanbini_set_card_labels

Set, add, or remove labels on a card in Kanbini by label id or name, replacing all labels, appending new ones, or taking specific ones off.

Instructions

Change a card's labels. labelIds are label ids or names (labels must belong to the card's board; make a missing one with kanbini_create_label). mode "replace" (the default) sets exactly these labels (an empty array removes all), "add" adds them to the ones it has, "remove" takes them off. A card can be given by its id, or by its number (#142, as shown on the card) with boardId (the id or name of the board it is on).

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": {
      "id": "<id>",
      "labelIds": "<labelIds>"
    },
    "name": "kanbini_set_card_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
modeNo
boardIdNoThe board's id or exact name. Needed when you name a card by number (#142) or a list / label by name.
labelIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.17.0
    • changedInput schema / properties / boardId / description
      Previous value: -"Only when a card is given by number (#142): the board it is on"New value: +"The board's id or exact name. Needed when you name a card by number (#142) or a list / label by name."
    • addedInput schema / properties / mode
      Added value: +{
      +  "enum": [
      +    "replace",
      +    "add",
      +    "remove"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.15.0
    • addedInput schema / properties / boardId
      Added value: +{
      +  "description": "Only when a card is given by number (#142): the board it is on",
      +  "type": "string"
      +}
  3. First observedv0.13.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that "replace" is the default and that an empty array removes all labels, which is the key destructive behavior an agent must not stumble into. It also states the domain constraint that labels must belong to the card's board. It stops short of saying what the call returns or whether changes are echoed back, so it falls just short of 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?

A single tight paragraph whose first sentence states the action, followed by parameter-specific clauses in priority order (labelIds, mode, card identification). No filler, no restatement of the title, and the most surprising behavior (default replace / empty array clears) is stated early.

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?

There is no output schema and no annotations, so the description must carry the full load for a 4-parameter mutation tool; it covers mutation semantics, defaults, referential constraints, and the create_label escape hatch. The only gap is the lack of any statement about the response (confirmation shape, resulting label set), which is a minor but real omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% (only boardId is self-documented), so the description must compensate, and it does: it defines labelIds as accepting ids or names, gives the exact accepted mode values with their semantics and default, and explains that id may be a raw id or a #142-style number requiring boardId. Every parameter gains meaning beyond the raw JSON schema.

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 opens with a specific verb+resource ("Change a card's labels") and immediately enumerates the three modes, so the agent knows this is a label-mutation tool rather than a general card update (kanbini_update_card) or a label-definition tool (kanbini_create_label). The title and body agree, and the scope is unambiguous.

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 states exactly when each mode applies ("replace" sets exactly these labels, "add" appends, "remove" detracts), names the default, and routes the agent to kanbini_create_label when a label doesn't exist. It also explains the two ways to reference a card (id, or #142 plus boardId), which is the main invocation ambiguity for this tool.

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