Skip to main content
Glama

KanbanMCP

Add or edit a column

edit_column

Adds a column, or changes one. Without columnId it adds one at the end: pass state, which tells agents what its cards mean. With columnId it renames the column, moves it, or both. A column's state never changes.

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

Input Schema

NameRequiredDescriptionDefault
labelNoThe label. Blank gives the state's name.
stateNolater, triage, todo, ready, running, blocked, review or done.
boardIdNoBoard id or slug.
personaNoThe persona to act as.
columnIdNoThe column to change, by id. Leave it out to add a column.
positionNoPlace in the board order, from 0. Left out when adding, the column goes last.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare it is a non-readOnly, non-idempotent, non-destructive write. The description adds real behavioral context beyond that: the invariant 'A column's state never changes', the default placement at the end when adding, and the persona-based acting model implied by the schema. It stops short of stating permission or auth requirements.

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 short sentences, front-loaded with the add/edit split, then mode-specific detail, then the state invariant. Every sentence carries distinct information and nothing is padded.

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 no output schema and six optional parameters, the description covers both modes, the append default, and the state invariant, which is enough for correct invocation. Minor gaps remain around required permissions and what a successful edit returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning: it explains the dual role of columnId, the positional default for position, and that state 'tells agents what its cards mean' — semantics the schema's enum list alone does not convey.

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 ('Adds a column, or changes one') and immediately distinguishes the two operating modes by presence of columnId. The scope is clear enough to separate it from delete_column and create_board without opening the schema.

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?

Explicit conditional routing: omit columnId to add (appended at the end), supply columnId to rename, move, or both. This tells the agent which mode to pick, though it names no alternative sibling tools or exclusion conditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources