Skip to main content
Glama

Delete Kanban Item

delete_kanban_item

Remove an item from a GitHub Kanban board without closing or deleting the underlying Issue or PR, keeping project tracking clean while preserving the source record.

Instructions

Remove an item from a GitHub Kanban board cleanly. This untethers it from the project but does NOT close or delete the underlying Issue/PR.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_kanban_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoRepository name - LEAVE EMPTY to auto-detect
ownerNoProject owner - LEAVE EMPTY to auto-detect
item_idNoThe project item ID to remove (from get_kanban_board)
use_test_dbNo
project_numberNoGitHub Project number (optional if repo is registered)

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
itemIdNo
detailsNoAdditional error context
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
projectNumberNo
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv9.1.0
    • changedInput schema / properties / project_number / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv9.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description meaningfully supports that by spelling out exactly what is and is not destroyed: the project linkage is severed, the issue/PR survives. It stops short of noting reversibility (can the item be re-added?) or permission requirements, and the "cleanly" wording is decorative rather than informative.

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?

Two short sentences, front-loaded with the action and followed by the critical scoping caveat. The word "cleanly" is the only filler, and it costs almost nothing against the clarity gained.

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?

With an output schema present and annotations covering the safety profile, the description only needs to convey intent and blast radius, which it does. The remaining gap is minor: all five parameters are optional, and nothing explains the auto-detect fallback chain for repo/owner/project_number at a behavioral level.

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 80% and the properties already carry the useful hints (item_id "from get_kanban_board", repo/owner "LEAVE EMPTY to auto-detect"). The description adds no parameter-level meaning, and notably is silent on use_test_db, which is undocumented in the schema as well; the baseline 3 applies given the schema does the heavy lifting.

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 ("Remove an item from a GitHub Kanban board") and immediately bounds the scope with "untethers it from the project but does NOT close or delete the underlying Issue/PR." That negative clause is what separates it from siblings like close_github_issue_with_entry or delete_entry, so an agent can route without opening a schema.

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

Usage Guidelines3/5

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

The "does NOT close or delete the underlying Issue/PR" line implies the correct situation (detaching board membership rather than removing content), but no alternative is named explicitly and no prerequisites are stated. Nothing tells the agent when to pick move_kanban_item, add_kanban_item, or close_github_issue_with_entry instead.

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

Deploy Server

Other Tools