Skip to main content
Glama

Delete a label

kanbini_delete_label

Remove a label from a board and strip it from every card that uses it, identified by id or name. Confirm intent first when the label is in use, since deletion affects all cards.

Instructions

Delete a label from its board. It is removed from EVERY card that carries it. The user can undo this in the app (Ctrl+Z), which puts it back on the same cards, but confirm intent first when the label is in use. Labels can be given by id or by name. (by name with boardId).

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>"
    },
    "name": "kanbini_delete_label"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.0
    • addedInput schema / properties / boardId
      Added value: +{
      +  "description": "The board's id or exact name. Needed when you name a card by number (#142) or a list / label by name.",
      +  "type": "string"
      +}
  2. First observedv0.13.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations present, the description carries the burden and does well: it discloses that deletion is board-wide across every card, that the user can recover via app undo (Ctrl+Z) restoring the same card associations, and that confirmation is warranted before committing. It omits any mention of required permissions or whether the delete is idempotent for a nonexistent label.

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?

Front-loaded with purpose and impact, then recovery semantics, then parameter addressing. Every sentence carries information, though the trailing parenthetical '(by name with `boardId`)' is fragmentary and duplicates what the previous sentence already implied.

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 two-parameter destructive tool with no annotations and no output schema, the description covers impact scope, reversibility, and addressing modes, which is most of what an agent needs. Missing only permission/prerequisite context and what a successful call returns.

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

Parameters4/5

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

Schema coverage is only 50% and the undocumented parameter is the required `id`, but the description compensates by stating it accepts either an id or a label name, and that name-based lookup requires `boardId`. That is meaningfully more than the schema conveys, though it gives no format hints for ids.

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 and resource ('Delete a label from its board') and immediately scopes the blast radius ('removed from EVERY card that carries it'). This distinguishes it from kanbini_update_label and kanbini_set_card_labels without the agent needing to open any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete operating condition: 'confirm intent first when the label is in use,' plus the alternate addressing mode with its prerequisite (name requires boardId). It does not name kanbini_set_card_labels as the non-destructive alternative for detaching a label from one card, which would have made this a 5.

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