Skip to main content
Glama

Update list settings

kanbini_update_list

Update a Kanban list's name, color, WIP limit, card sort order, on-enter rule, or display density.

Instructions

Patch a list (column). name renames it. color tints the list header and border (null clears it). wipLimit sets a work-in-progress cap - a positive integer, or null to remove it; the app shows the count against the cap and blocks drags past it, but the limit is NOT enforced for writes, so check the card count yourself before adding. sortMode orders the cards: "manual" (drag order, the default), "created-asc"/"created-desc" (card creation time), "added-asc"/"added-desc" (when the card entered this list), "due-asc" (soonest due first, undated last), "title-asc"/"title-desc" (alphabetical), "priority-desc" (urgent first). Switching back to "manual" freezes the current sorted order as the new drag order. onEnter runs when a card is moved INTO this list from another one: "complete" marks it done, "uncomplete" reopens it, null removes the rule. cardDensity "compact" draws every card in the list compact (a card can opt out with kanbini_update_card collapsed: false); "full" is the default. visibleCardLimit shows at most that many cards on screen, then a "Show N more" button (1-1000); 0 always shows every card; null (the default) lets the app shorten a list of more than 30 cards to its first 20 (the user can turn that off). Both are display only: the reads always return EVERY card, so never read a limit as the list being shorter. Change them only when the user asks. To reorder lists use kanbini_move_list; to hide one use kanbini_archive_list. A list can be given by its id, or by its exact 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_list"
  }
}

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. Changed1 schema field changedv0.16.0
    • changedInput schema / properties / patch / properties / visibleCardLimit / anyOf
      Previous value: -[
      -  {
      -    "exclusiveMinimum": 0,
      -    "maximum": 1000,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 1000,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. First observedv0.13.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so unusually well: it discloses that the WIP limit is display-only and NOT enforced on writes (advising a manual count check), that switching sortMode to 'manual' freezes the current sorted order as drag order, that visibleCardLimit is purely cosmetic and reads always return every card, and that null clears color/wipLimit/onEnter.

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 the core purpose, and nearly every clause adds information. However, the body is a single dense block covering seven fields plus two cross-references; per-field line breaks or bullets would make the enum semantics much easier to scan without losing content.

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

Completeness5/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 annotations and no output schema, this is complete: it covers safety-relevant behavior (unenforced WIP limit, order freezing), display-vs-data divergence, null semantics for clearing, and identification modes. Nothing an agent needs to invoke it correctly is missing.

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 33%, but the description compensates by defining every nested patch field: what `name` does, that `color` accepts palette names for swatch consistency, that `wipLimit` must be positive or null, and the exact semantics of each sortMode value including how undated cards sort and what 'added' vs 'created' time means. That is meaning well beyond the schema's bare enums and types.

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?

Opens with a specific verb+resource ('Patch a list (column)') and then enumerates every patchable field, so the agent knows exactly what the tool mutates. It also names the sibling tools that handle adjacent operations (kanbini_move_list for reordering, kanbini_archive_list for hiding), making it distinguishable without opening another schema.

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?

Explicit routing: reorder goes to kanbini_move_list, hiding goes to kanbini_archive_list, and display-only settings should be changed 'only when the user asks'. It also states the two ways to identify a list (id, or exact name plus boardId), which is the key precondition for calling it correctly.

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