Skip to main content
Glama

create_task

Create a new task on a Kanban board. Requires only a task name and board ID; supports optional lane, assignee, priority, due date, and tags.

Instructions

Create a new task on a board. Only name and board_id are required.

lane_id is the target column (matches Task.lane_id on fetched tasks). assigned_user_id sets the single assignee — Kanban Tool tasks have one assignee, not a list. (The API silently ignores a legacy assignees: [int] payload on writes, so this kwarg is the wire field name directly.) priority accepts the string enum or the raw integer; tags is a comma-separated string; due_date is an ISO 8601 string forwarded as-is. Unset kwargs are omitted from the request, never sent as explicit null.

Common 422s (KanbanToolValidationError with parsed field_errors): name empty/missing → fix by passing a non-empty string; lane_id belongs to a different board → resolve column ids on the target board first via get_board(board_id).columns; assigned_user_id not a board collaborator → check via list_board_collaborators(board_id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
board_idYes
descriptionNo
lane_idNo
positionNo
assigned_user_idNo
due_dateNo
priorityNo
tagsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes
descriptionNo
board_idNo
workflow_stage_idNo
swimlane_idNo
positionNo
priorityNo
colorNo
due_dateNo
start_dateNo
tagsNo
assigned_user_idNo
archived_atNo
block_reasonNo
subtasks_countNo
subtasksNo
comments_countNo
timers_totalNo
time_trackersNo
created_atNo
updated_atNo
size_estimateNo
size_estimate_descriptionNo
time_estimateNo
search_tagsNo
card_colorNo
card_color_in_rgbNo
card_color_invertNo
card_type_idNo
recurring_scheduleNo
reminders_scheduleNo
linked_tasksNo
linked_tasks_statusNo
task_dependenciesNo
collaboratorsNo
attachmentsNo
attachments_countNo
created_by_idNo
moved_atNo
postponed_untilNo
subtasks_completed_countNo
external_idNo
external_linkNo
custom_fieldsNo
is_archivedYesTrue iff the task has an archival timestamp.
is_blockedYesTrue iff the task has a non-empty block reason.
Behavior5/5

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

Annotations indicate non-destructive mutation. Description adds beyond annotations: notes that unset kwargs are omitted, API silently ignores legacy assignees array, and details error handling. No contradiction with annotations.

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?

Description is somewhat lengthy but well-structured: front-loaded with purpose and required fields, then optional parameters, then common errors. Every sentence adds value, though slight trimming could improve conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 9 parameters, 2 required, and an output schema (not shown), the description covers all aspects: required params, optional param semantics, error handling, and usage context. It is complete and leaves no significant gaps.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining each parameter's semantics: lane_id matches Task.lane_id, assigned_user_id is a single assignee, priority accepts string enum or integer, tags is comma-separated, due_date ISO 8601, and behavior for unset fields.

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?

The description clearly states 'Create a new task on a board.' and specifies required parameters (name and board_id). It distinguishes from sibling tools like update_task and archive_task by focusing on creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description provides explicit guidance on when to use, including required fields and common error scenarios (422s) with troubleshooting links to get_board and list_board_collaborators, effectively telling the agent when and when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VeryLongOrgNameSuchWow/kanbantool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server