Skip to main content
Glama

Coline

Create a task

create_task

Creates a task on a board. Without a status it lands in the board's default status.

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": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "title": "<title>"
    },
    "name": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
labelsNo
dueDateNo
priorityNo
statusIdNoStatus id from the board's statuses.
timeZoneNoIANA time zone for the time block.
waitingOnNoWho the task is waiting on; null clears it.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
descriptionNoPlain text; each line becomes a paragraph.
taskboardIdYesBoard id from list_boards.
parentTaskIdNoMake it a sub-task of this task (same board).
scheduledEndNoEnd of the calendar time block.
assigneeEmailsNoAssign by email instead of id; each must be a workspace member.
scheduledStartNoStart of a calendar time block. Pair with scheduledEnd.
assigneeUserIdsNoWorkspace member ids.
clientRequestIdNoSend the same id on a retry to avoid a second task.
sourceMessageIdNoThe message this task came from.
attachmentFileIdsNoImage file ids to show inline in the description.
customFieldValuesNo
descriptionBlocksNoRich description blocks, as Coline's editor stores them.

Output Schema

NameRequiredDescriptionDefault
taskYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is known. The description usefully adds a defaulting behavior for omitted status, which is genuine context beyond the annotations, but says nothing about required permissions, board membership constraints, or the non-idempotency implication (retries creating duplicates) that matters for a create tool.

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?

Two short sentences, both front-loaded with the most important fact first and the defaulting rule second. No filler, no restatement of the title, nothing wasted.

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

Completeness3/5

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

The tool is complex (20 parameters, a mutation, rich nested custom-field values) but the schema descriptions plus an output schema carry most of the load. The description covers creation and the status default but omits the broader defaulting/validation story an agent would want before constructing a large payload, making it minimally adequate rather than complete.

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 description coverage is 75%, so the schema already documents most of the 20 parameters, including clientRequestId for retry safety and the assignee/custom-field fields. The description adds one real semantic point the schema lacks: statusId is optional and defaults to the board's default status. It adds nothing about the other optional fields or interactions between them (e.g., assigneeEmails requiring workspace membership is only in the schema).

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?

The description gives a specific verb and resource ("Creates a task on a board"), which matches the title and distinguishes it from siblings like create_taskboard or create_task_view. It stops short of explicitly contrasting this tool with nearby task-creation-adjacent siblings such as add_task_blocker or attach_to_task, so an agent must infer that this is the primary creation entry point.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternatives. The only conditional statement ("Without a status it lands in the board's default status") is about behavior, not about tool selection, so the agent gets no routing help.

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