Skip to main content
Glama

KanbanMCP

Create a card

create_card

Creates a card with all its fields in one call. Pass copyFrom to copy another card. Pass cards to create several at once. It lands in Triage unless you pass state or column. Each card counts toward the plan's limit.

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

Input Schema

NameRequiredDescriptionDefault
bodyNoThe description (markdown).
parkNoWith snoozeUntil: park in Snoozed. Default true.
cardsNoSeveral cards: each takes the fields above.
claimNoTake the new card in the same call. The reply is the claim.
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.
stateNolater, triage, todo, ready, running, blocked, review or done.
titleNo
branchNo
columnNoA column, by id or label.
effortNolow, medium or high.
labelsNoThe whole set. addLabels and removeLabels change some.
tenantNoA group, such as a client.
uniqueNoRefuse if a similar card exists.
boardIdNoBoard id or slug.
commentNoAn opening comment. @name notifies.
parentsNoCards that must finish first, by number or key.
personaNoThe persona to act as.
verboseNoReturn the whole card.
assigneeNoA persona name. Null clears it.
copyFromNoA card to copy. Fields you pass replace its.
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
checklistNoThe whole checklist: {text, done} items.
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.
idempotencyKeyNoThe same key again returns the same card.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, non-destructive, non-idempotent write. The description adds real behavioral context beyond that: the default destination is Triage unless state/column are supplied, and each card counts against the plan's limit. It stops short of describing the response shape or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short, front-loaded sentences that each carry distinct information (creation, copy, batch, default placement, quota). Minimal waste, though 'with all its fields in one call' is slightly redundant padding.

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 42-parameter tool with 90% schema coverage and no output schema, the description covers the key defaults (Triage placement, plan limit) an agent would otherwise miss. Return-format behavior is left to the verbose parameter in the schema, which is acceptable.

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 coverage is 90%, so the schema already documents nearly all 42 parameters in detail. The description calls out copyFrom, cards, state, and column, but those clarifications largely restate what the schema descriptions already say, adding little syntax or semantics beyond it. Baseline 3 is appropriate.

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?

States a specific verb+resource ('Creates a card') and clarifies the scope ('with all its fields in one call'), so the agent knows this is the single-call creation entry point. It does not explicitly differentiate itself from the closest sibling update_card, but create-vs-update is unambiguous from the verb.

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 gives conditional usage for parameters ('Pass copyFrom...', 'Pass cards to create several at once') and states the default landing spot ('lands in Triage unless you pass state or column'). However, it offers no guidance on when to choose create_card over update_card or other creation-adjacent siblings, leaving tool selection to inference.

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