Skip to main content
Glama

Move Kanban Item

move_kanban_item
Idempotent

Move a Kanban item to a different status column; requires a project board Status field and uses target status, item ID, and project or repo details.

Instructions

Move a Kanban item to a different status column. Requires the project board to have a Status field.

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": "move_kanban_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoRepository name - LEAVE EMPTY to auto-detect
ownerNoProject owner - LEAVE EMPTY to auto-detect
item_idNoProject item ID (from get_kanban_board)
use_test_dbNo
target_statusNoTarget status column name (e.g., "In Progress", "Done")
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)
newStatusNo
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
projectNumberNo
aggregated_errorsNoDetails of individual errors in a multi-step operation
availableStatusesNo

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

A3.6/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), so the description needn't restate them. It contributes the Status-field prerequisite, which is genuinely useful and not encoded elsewhere, but says nothing about failure behavior, authentication requirements, or what happens when the item is already in the target column.

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 with the action front-loaded and the constraint immediately after; every clause carries information and there is no filler.

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 strong schema coverage, the description only needs to convey purpose and preconditions, which it does. The minor gap is that the prerequisite is stated without saying what error surfaces or how to verify the Status field exists before calling.

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 83%, so parameter meaning is largely carried by the schema (auto-detect for repo/owner, item_id sourced from get_kanban_board, example status names). The description adds no extra semantics about target_status matching rules (exact string vs case-insensitive) or the optional project_number.

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?

The description states a specific verb and resource ('Move a Kanban item to a different status column'), which is unambiguous about the action taken. It does not explicitly distinguish itself from siblings like add_kanban_item, delete_kanban_item, or get_kanban_board, though the verb makes the difference largely self-evident.

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?

It adds one real precondition ('Requires the project board to have a Status field'), which tells the agent when the call will fail. However, it gives no guidance on obtaining item_id via get_kanban_board, no alternatives to consider, and no note on what to do when the target column is missing.

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