Skip to main content
Glama

Create a card

kanbini_create_card

Create a Kanban card in one call with title, description, due date, priority, labels, checklists, and optional position in a list.

Instructions

Create a card, complete in ONE call: title plus any of description (Markdown, with real line breaks), due (YYYY-MM-DD) or dueAt (epoch ms at local midnight), priority ('low' | 'medium' | 'high' | 'urgent'), labels (names or ids of labels on that board; make a missing one with kanbini_create_label), checklists ([{ name, items: [text, ...] }]), repeat, and completed. It goes at the end of the list unless you give beforeId (the card that will sit directly ABOVE it) or afterId (the card directly BELOW). Returns { id, boardId }. Respect a list's wipLimit: it is advisory and not enforced, so check the card count before adding when one is set. A list can be given by its id, or by its exact name with boardId. Labels by name and cards by number need boardId too.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listId": "<listId>",
      "title": "<title>"
    },
    "name": "kanbini_create_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNoLocal calendar day, YYYY-MM-DD
dueAtNo
titleYes
labelsNo
listIdYes
repeatNo
afterIdNoCard that will sit directly BELOW the new card
boardIdNoThe board's id or exact name. Needed when you name a card by number (#142) or a list / label by name.
beforeIdNoCard that will sit directly ABOVE the new card
priorityNo
completedNo
checklistsNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.17.0
    • addedInput schema / properties / afterId
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Card that will sit directly BELOW the new card"
      +}
    • addedInput schema / properties / beforeId
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Card that will sit directly ABOVE the new card"
      +}
    • addedInput schema / properties / boardId
      Added value: +{
      +  "description": "The board's id or exact name. Needed when you name a card by number (#142) or a list / label by name.",
      +  "type": "string"
      +}
    • addedInput schema / properties / checklists
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "items": {
      +        "items": {
      +          "minLength": 1,
      +          "type": "string"
      +        },
      +        "maxItems": 200,
      +        "type": "array"
      +      },
      +      "name": {
      +        "minLength": 1,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedInput schema / properties / completed
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / due
      Added value: +{
      +  "description": "Local calendar day, YYYY-MM-DD",
      +  "type": "string"
      +}
    • addedInput schema / properties / dueAt
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / labels
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / repeat
      Added value: +{
      +  "properties": {
      +    "every": {
      +      "maximum": 99,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "unit": {
      +      "enum": [
      +        "day",
      +        "week",
      +        "month",
      +        "year"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "unit",
      +    "every"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.13.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the return shape ({ id, boardId }), the default side effect that the card lands at the end of the list, the exact positional semantics of beforeId/afterId, and the non-obvious fact that wipLimit is advisory and unenforced. It does not cover failure modes (invalid list name, unknown label) or permission requirements.

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?

It is one dense paragraph, but front-loaded with the action and every clause carries new information (format hints, positional rules, wipLimit caveat). A bulleted structure would read faster, yet there is no filler to cut.

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 13-parameter create tool with nested objects and no output schema, the description covers the required fields, the nested checklists shape, positioning, and even the return value. What remains missing is error behavior and defaults for unset fields like priority, which is modest for a create operation.

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 only 31%, so the description must compensate and largely does: it explains due format, dueAt as epoch ms at local midnight, priority enum values, labels accepting names or ids, the checklists shape, and the boardId requirement for name-based list/label/card references. Only `repeat`'s internal structure and the `completed` semantics are left entirely to the schema, which is a small remaining gap across 13 parameters.

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 ('Create a card') and immediately scopes it as 'complete in ONE call', which implicitly separates it from kanbini_update_card / copy_card / batch. The agent can pick this tool without inspecting siblings.

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?

Gives concrete when-to guidance: create the full card in one call rather than create-then-update, use kanbini_create_label for missing labels, check the card count before adding when a list has a wipLimit. It stops short of naming exclusions (e.g., when to prefer kanbini_batch or copy_card instead), so it is clear context without full alternative routing.

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