Skip to main content
Glama

Archive or restore a list

kanbini_archive_list

Archive or restore an entire Kanbini list (column) by id or exact name with boardId; archived lists and their cards hide from the board, search, and counts without deleting data.

Instructions

Archive (archived: true) or restore (archived: false) a whole list (column). An archived list is hidden from the board along with every card in it, and its cards drop out of search and counts; nothing is deleted, and restoring brings the list back in its original slot with its cards. Tell the user: they can see and restore it in the app from the board's pencil menu > Archived..., and kanbini_list_archived finds it too. A list can be given by its id, or by its exact 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>",
      "archived": "<archived>"
    },
    "name": "kanbini_archive_list"
  }
}

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.
archivedYes

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.5/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 behavioral burden and does it well: it discloses the side effects (list hidden from the board, its cards vanish from search and counts), the fact that nothing is destroyed, and the exact restore semantics (original slot, cards included). It stops short of error behavior (already archived, unknown id) and any permission or authorization requirements.

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 verb/resource and the flag values, followed by consequences and then a user-facing note. Every sentence adds information, though the 'Tell the user' sentence is a bit of an instruction-in-description and could be tighter.

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 3-parameter mutation tool with no annotations and no output schema, the definition covers effects, reversibility, restore semantics, discovery of archived items, and how to address the list. The only gap is what the response contains, which is minor for a toggle operation.

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% — only boardId is documented — so the description must compensate, and it does: it explains that `archived` is a boolean switch selecting archive vs. restore, and that `id` accepts either an id or an exact name, with `boardId` required in the name case. That is meaningful semantics beyond the bare schema 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?

States a specific verb pair with the parameter values that select them ('Archive (archived: true) or restore (archived: false) a whole list (column)'), so both directions are unambiguous. The '(column)' clarification disambiguates from other list-like concepts and distinguishes it from siblings such as kanbini_archive_card and kanbini_delete_list.

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 context for when to use it and points at kanbini_list_archived as the companion tool for finding archived lists, plus the in-app path for the human. It does not explicitly contrast against kanbini_delete_list for permanent removal, so the when-not-to-use case is only implied by 'nothing is deleted'.

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