Skip to main content
Glama

Rename or recolour a label

kanbini_update_label

Rename or recolor an existing Kanbini label by ID or name; the change applies to every card carrying that label so board categories stay consistent.

Instructions

Patch a label. name renames it and color recolours it - the change shows on every card carrying the label. Omit fields you do not want to change. Labels can be given by id or by name. (by name with boardId). Colours: pass a palette name (red, orange, amber, yellow, lime, green, teal, cyan, sky, blue, indigo, purple, pink, rose) so it matches the app's swatch picker.

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

Input Schema

NameRequiredDescriptionDefault
idYes
patchYes
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.1/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 disclosure burden and does reasonably well: it warns that a rename or recolour 'shows on every card carrying the label', which is a non-obvious propagation side effect, and clarifies that only supplied fields are mutated. It omits permission requirements, name-collision behaviour, and error cases for an unresolved label name.

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-loads the action and the field meanings, then tacks on targeting rules and the colour palette. The parenthetical '(by name with `boardId`)' is awkwardly placed and slightly redundant with the `boardId` schema description, but the overall length is justified by the information density.

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 nested-object mutation with no annotations and no output schema, the description covers the essentials: what changes, what propagates, how to address the label, and acceptable colour formats. Remaining gaps (error behaviour on unknown label names, permission needs) are minor for a simple rename/recolour patch.

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 description coverage is only 33% (the bare `id` and `patch.name` params have no schema descriptions), and the description partially compensates by explaining that `id` accepts an id or a name plus `boardId`, and that `patch.name` performs the rename. However, the palette enumeration it lists largely duplicates the existing `color` schema description, so the net added meaning is modest.

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 ('Patch a label') and immediately enumerates the two mutable fields and their effects. This cleanly separates it from kanbini_create_label, kanbini_delete_label, and kanbini_set_card_labels, which concern label lifecycle or card-label assignment rather than label metadata.

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 clear operational guidance: 'Omit fields you do not want to change' establishes partial-update semantics, and 'Labels can be given by id or by name (by name with `boardId`)' tells the agent how to target the resource. It does not explicitly name alternatives (e.g. use set_card_labels to attach the label to cards), so it stops short of full when/when-not routing.

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