Skip to main content
Glama

KanbanMCP

Update a card

update_card
DestructiveIdempotent

Changes any of a card's fields in one call, and archives or restores it (archived). Fields you leave out stay as they are. Pass updates to change several cards at once. Pass checklist as {add, remove} to change items in place. To move a card use move_card. A field that changed since you read the card refuses the call: call show, then write again.

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

Input Schema

NameRequiredDescriptionDefault
bodyNoThe description (markdown).
parkNoWith snoozeUntil: park in Snoozed. Default true.
dueAtNoA due date. Needs the board's due dates setting.
ownerNoA person (name or id) to own a card with no owner.
prUrlNoThe pull request (https).
recurNoRepeat the card: every (daily, weekly, monthly), at, to. Null stops it.
titleNo
branchNo
cardIdNoCard id, number (12) or key (WEB-12).
effortNolow, medium or high.
labelsNoThe whole set. addLabels and removeLabels change some.
tenantNoA group, such as a client.
boardIdNoBoard id or slug.
personaNoThe persona to act as.
updatesNoSeveral cards: each has cardId and the fields above.
verboseNoReturn the whole card.
versionNoThe card version show gave you. Left out, this connection's last read counts.
archivedNoTrue archives, false restores.
assigneeNoA persona name. Null clears it.
estimateNoXS, S, M, L or XL. Needs the board's estimates setting.
expediteNoLet the card pass the WIP cap and be claimed first.
goalModeNoKeep going until the acceptance criteria hold.
maxTurnsNoTurns in goal mode. Null clears it.
priorityNo3 urgent, 2 high, 1 normal, 0 low.
addLabelsNo
checklistNoAn array replaces the list with {text, done} items. An object changes it: {add: [texts], remove: [positions from 1, or texts]}.
modelHintNoA model the work suits.
ownerNoteNoWhy, for that person.
skillPinsNoSkills to load first.
acceptanceNoWhat done means. Null clears it.
touchPathsNoFiles it will touch.
snoozeUntilNoHide the card until this date. Null clears it.
circuitLimitNoFailures that stop claims of the card.
maxRuntimeMsNoLongest run in milliseconds. Null clears it.
removeLabelsNo
verifyCommandNoThe command that proves it.
workspaceHintNoWhere the work happens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare it destructive and idempotent; the description goes well beyond them by disclosing partial-update semantics ('Fields you leave out stay as they are'), optimistic-concurrency conflict handling ('call show, then write again'), and in-place checklist mutation. This is exactly the extra context annotations cannot carry.

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?

Five tight sentences, front-loaded with the core mutate/archive action, then bulk, then checklist, then the routing note and conflict caveat. No sentence is 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?

For a 37-parameter destructive tool with no output schema, it covers the high-risk behaviors (conflict refusal, partial updates, bulk mode) that an agent must know. It leaves permission requirements and the effect of persona/tenant scoping unstated, so it is complete but not exhaustive.

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 89%, so the baseline is 3, but the description adds meaning the schema lacks: merge vs replace behavior for omitted fields, the {add, remove} checklist shape, and the multi-card 'updates' pattern. It does not explain version/persona/verbose interactions, so it is not a 5.

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 (changes/updates) and resource (a card), including the archive/restore facet, and explicitly distinguishes itself from move_card. An agent can separate this from create_card, move_card, and toggle_task without opening schemas.

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?

Names the alternative for relocation ('To move a card use move_card') and gives the bulk-update path via 'updates', which is clear routing guidance. It stops short of stating when not to use it (e.g. single-field label changes vs label tool), so it is strong but not exhaustive.

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