Skip to main content
Glama

create_task

Create a new TickTick task with title, project, due date, priority, tags, checklist items, and reminders. For subtasks, use set_subtask_parent after creation.

Instructions

Create a new TickTick task.

[Category: Tasks — Write]  [Auth: V1]
[Related: update_task, complete_task, set_subtask_parent, build_recurrence_rule]
[Workflow: For subtasks → create_task then set_subtask_parent]

⚠️ SUBTASK TRAP — parentId is SILENTLY IGNORED by the V1 creation endpoint.
Passing parentId in the payload creates a standalone task with no error or warning.
ALWAYS use set_subtask_parent AFTER creation to establish the relationship.
Correct sequence: create_task (parent) → create_task / batch_create_tasks (children) → set_subtask_parent × N

Args:
    title: Task title (required).
    project_id: Target project ID. Omit → Inbox.
    content: Body / description (plain text or markdown).
    desc: Alt description field (used by some TickTick views).
    priority: 0=none, 1=low, 3=medium, 5=high (Eisenhower: 5=urgent+important).
    due_date: ISO 8601, e.g. "2026-03-10T09:00:00+0000".
    start_date: ISO 8601.
    time_zone: IANA timezone, e.g. "Europe/Paris". Recommended with dates.
    tags: Tag strings, e.g. ["work", "urgent"].
    checklist_items: Strings → each becomes a checklist item. Auto-sets kind=CHECKLIST.
    all_day: True for all-day (no specific time).
    kind: "TEXT", "NOTE", or "CHECKLIST". Auto-set if checklist_items given.
    reminder_minutes: Minutes before due to remind, e.g. [0, 30, 1440].
        0=at time, 30=30min before, 1440=1 day before.
    recurrence: RRULE string (use build_recurrence_rule to generate).
    column_id: Kanban column ID (for kanban-view projects).

Returns the created task with its assigned id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
project_idNo
contentNo
descNo
priorityNo
due_dateNo
start_dateNo
time_zoneNo
tagsNo
checklist_itemsNo
all_dayNo
kindNo
reminder_minutesNo
recurrenceNo
column_idNo
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses the critical behavioral detail that parentId is silently ignored, and notes auto-setting of kind when checklist_items are provided. It states it returns the created task with id. However, it does not discuss error handling, rate limits, or idempotency. Good but not exhaustive.

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?

The description is well-structured with a header, prominent warning box, and parameter list. It is relatively long but each section serves a purpose. The warning box is justified given the critical subtask pitfall. Slightly verbose in places (e.g., repeating 'Tags' as array), but overall efficient.

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 the tool's complexity (15 parameters, no annotations, no output schema), the description covers all necessary aspects: parameter explanations, a critical behavioral warning, return value, and integration with related tools. It provides a complete mental model for using this tool correctly.

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?

Schema description coverage is 0%, so the description must compensate. It provides detailed semantics for all 15 parameters, including types, defaults, and specific values (e.g., priority mapping, reminder_minutes format). Examples are given for dates and tags. This adds significant value beyond the bare schema.

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 starts with 'Create a new TickTick task' which is a clear verb+resource combination. It explicitly distinguishes from related tools like update_task and complete_task, and provides workflow context for subtasks. This leaves no ambiguity about what the tool does.

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?

The description includes explicit when-to-use guidance (task creation) and a prominent warning about the subtask trap, advising to use set_subtask_parent instead. It also mentions batch_create_tasks for batch operations, and categorizes the tool under 'Tasks — Write'. This makes selection vs siblings clear.

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/KpihX/tick-mcp'

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