Skip to main content
Glama

create_task

Create a new project task with initial status, assignee, subtask parent, priority, labels, and due date; check list_tasks first to avoid duplicates.

Instructions

Create a new task in a project and return it with its id. status_slug sets the initial status (defaults to the project's first status); assignee_id with assignee_type routes it to someone; parent_task_id makes it a subtask. Search list_tasks first so you do not file a duplicate.

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

Input Schema

NameRequiredDescriptionDefault
titleYesTask title.
labelsNoTask labels.
due_dateNoDue date in RFC3339 format.
priorityNoPriority: urgent, high, medium, low, none.medium
project_idYesUUID of the project to create the task in (list_projects returns ids).
assignee_idNoAssignee ID (user or agent UUID).
descriptionNoTask description.
start_afterNoHold the task out of the queue until this moment, RFC3339 with Z or an offset (2026-11-01T09:00:00+03:00). From an agent it must be the published time of an external event, given with start_after_evidence; not a retry or poll interval. Independent of due_date.
status_slugNoStatus slug (e.g. 'todo'). Uses project default if omitted.
assignee_typeNoAssignee type: user, agent.unassigned
custom_fieldsNoCustom field values as key-value pairs.
parent_task_idNoParent task ID for subtask.
estimated_hoursNoEstimated hours for the task.
delegation_levelNoDelegation level: auto, review, supervised.
start_after_originNoOptional, only agent_evidence. The server derives the origin from the caller; a person's date needs no evidence.
start_after_evidenceNoRequired by the server for an agent's start_after: {event_ref, source, why}, the same rules as wait_for on=time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.7
    • changedInput schema / properties / start_after / description
      Previous value: -"Don't surface/feed this task before this RFC3339 timestamp (e.g. a scheduled retry). Independent of due_date."New value: +"Hold the task out of the queue until this moment, RFC3339 with Z or an offset (2026-11-01T09:00:00+03:00). From an agent it must be the published time of an external event, given with start_after_evidence; not a retry or poll interval. Independent of due_date."
    • addedInput schema / properties / start_after_evidence
      Added value: +{
      +  "description": "Required by the server for an agent's start_after: {event_ref, source, why}, the same rules as wait_for on=time.",
      +  "properties": {
      +    "event_ref": {
      +      "description": "The external event the moment belongs to, e.g. nightly-export (max 500 chars).",
      +      "type": "string"
      +    },
      +    "source": {
      +      "description": "Where the event's time is published: an https:// URL, comment:<uuid> or artifact:<uuid> written by someone else.",
      +      "type": "string"
      +    },
      +    "why": {
      +      "description": "What happens at start_after and why not earlier, 10 to 500 chars.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / start_after_origin
      Added value: +{
      +  "description": "Optional, only agent_evidence. The server derives the origin from the caller; a person's date needs no evidence.",
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID."New value: +"UUID of the project to create the task in (list_projects returns ids)."
  3. First observedv0.1.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare the non-read-only, non-destructive, non-idempotent profile, so the safety burden is lighter here. The description adds real context — it returns the created task with its id, status_slug defaults to the project's first status, and assignee_id must be paired with assignee_type. It says nothing about failure behavior (duplicate titles, invalid project_id, missing start_after_evidence) or what the response contains beyond the id.

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?

Three compact clauses ordered by importance: what it does and returns, then the optional shaping knobs, then the duplicate-avoidance instruction. Every sentence carries a distinct piece of information with no 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 16-parameter creation tool with a nested evidence object and no output schema, the description covers the decisions an agent most often gets wrong (status default, assignee pairing, subtask nesting, duplicates). The complex start_after/start_after_evidence rules are fully spelled out in the schema, so their absence from the description is a minor gap rather than a hole.

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 100%, so the baseline is 3, but the description earns an increment by stating the coupling between assignee_id and assignee_type and the default resolution of status_slug — relationships the schema documents only per-field. The remaining 12 parameters (start_after evidence rules, delegation_level, custom_fields, priority) are left entirely to the schema, which is acceptable given its richness.

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?

"Create a new task in a project and return it with its id" is a specific verb+resource+return statement, so the agent knows exactly what it gets back. It partially differentiates from siblings by explaining that parent_task_id makes a subtask, but it never names create_subtask or create_recurring_task, which are the closest neighbors and a plausible source of mis-selection.

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?

It gives a concrete pre-flight instruction naming a sibling: "Search list_tasks first so you do not file a duplicate." That is genuine routing guidance, not just context. It stops short of exclusions such as when to use create_recurring_task or create_subtask instead, so the coverage is one-sided.

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