Skip to main content
Glama

Delete a card

kanbini_delete_card

Permanently delete a Kanbini card by ID or board and card number, removing its checklists, comments, and attachment rows; confirm intent because deletion cannot be undone.

Instructions

Permanently delete a card. Its checklists, comments, and attachment rows are removed by the FK cascade. Files attached to the card stay on disk until the GC sweep - they cannot be restored from the UI, so confirm intent before calling. 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>"
    },
    "name": "kanbini_delete_card"
  }
}

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
    • 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."
  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.5/5.0
Behavior5/5

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

With no annotations at all, the description carries the full burden and does so: it discloses cascade deletion of checklists, comments, and attachment rows, notes that files persist on disk until a GC sweep, and flags irreversibility. That is exactly the destructive-behavior context an agent needs before calling.

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?

Three tight sentences: destruction scope first, the irreversibility warning second, and the identifier forms last. No filler, and the highest-stakes information is front-loaded.

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 consequences and argument forms well. It does not say what a successful call returns or whether any permission is required, which are minor remaining gaps.

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 50% and the `id` property is undocumented in the schema, but the description compensates by explaining that a card may be given by id or by number (`#142`), and that `boardId` (id or exact name) is required in the number case. Both parameters gain meaning beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Permanently delete a card" gives a specific verb and resource, and the word "Permanently" implicitly separates it from the sibling kanbini_archive_card. It never names that sibling explicitly, so the agent must infer the archive-vs-delete distinction.

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?

It states a clear precondition ("confirm intent before calling") and notes the action cannot be restored from the UI, which effectively signals when to prefer a non-destructive path. It stops short of naming kanbini_archive_card as the alternative for reversible removal.

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