Skip to main content
Glama

create_task

Create a new task by specifying its status, title, description, priority, assignees, and due dates.

Instructions

Create a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTag names to apply to the task on creation (native — set in one call).
SpaceNoOptional sub-space ID for further scoping inside the workspace.
extraNoFree-form payload (`_extra` on the model).
orderNo
titleNo
parentNoParent task UUID (for subtasks).
statusYesTarget status UUID.
completeNo
due_dateNo
priorityNoPriority enum value.
assigneesNoInteger user IDs to assign (get from listWorkspaceMembers). Composite field — toolkit calls POST /tasks/{id}/assignees/ automatically after creation. Note: assignees are NOT in the createTask response; use getTask?expand=assignees to verify.
task_typeNoTask discriminator. Defaults to `TASK`.
start_dateNo
descriptionNoPlain text task description. This is the field agents and CLI users should set. The toolkit converts it to a Quill Delta and writes `rich_description` automatically.
OrganizationNoWorkspace (organization) ID the request is scoped to.
custom_fieldsNoMap of custom field UUID → value. Validated against board's custom-field configuration.
estimated_hoursNoEstimated completion time in hours.
rich_descriptionNoINTERNAL — Quill Delta representation. Set automatically by the toolkit when you pass `description`. Do not pass directly unless you have a pre-built Delta and know what you're doing.
Behavior2/5

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

Without annotations, the description carries full burden. It only says 'Create a task', omitting behavioral traits such as the required status field, auto-assignment of assignees, or the conversion of plain text description to rich_description. The schema parameter descriptions provide some context, but the description itself is silent.

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

Conciseness2/5

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

The description is a single sentence, but it is under-specified rather than concise. Every sentence should earn its place; this one fails to provide adequate context for a tool with 18 parameters.

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

Completeness1/5

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

Given the 18 parameters, no annotations, and no output schema, the description is severely incomplete. It does not explain return values, side effects, required prerequisites (e.g., Organization ID), or complex behaviors like custom_fields and assignees.

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?

With 72% schema description coverage, the baseline is 3. The tool description adds no additional information beyond the schema, so it neither improves nor degrades the parameter understanding.

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 clearly states the verb 'Create' and resource 'task', conveying the core action. However, it does not distinguish this tool from siblings such as 'clone_task' or 'create_project_item', which have overlapping concepts.

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?

No guidance is provided on when to use this tool versus alternatives like 'clone_task' or 'create_project_item'. There are no examples, prerequisites, or exclusions mentioned.

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/celeryhq/simplified-mcp-server'

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