Skip to main content
Glama

create_tasks

Create one or multiple TickTick tasks at once, including due dates, priorities, reminders, and subtasks, to streamline task management.

Instructions

Create one or more tasks in TickTick.

Supports both single task and batch creation. For single task, you can pass a dictionary directly. For multiple tasks, pass a list of dictionaries.

Args: tasks: Task dictionary or list of task dictionaries. Each task must contain: - title (required): Task Name - project_id (required): ID of the project for the task - content (optional): Task description - desc (optional): Description of checklist - start_date (optional): ISO datetime WITH timezone offset (e.g., 2025-12-16T08:00:00+0000) - due_date (optional): ISO datetime WITH timezone offset - time_zone (required): IANA timezone name (e.g. "Asia/Shanghai") - priority (optional): Priority level - "none", "low", "medium", or "high" - repeat_flag (optional): Recurring rules (e.g., "RRULE:FREQ=DAILY;INTERVAL=1") - items (optional): List of subtask dictionaries - reminders (optional): List of iCal TRIGGER strings. Without this, NO alarm fires even if due_date is set. Examples: ["TRIGGER:PT0S"] → at due time ["TRIGGER:-PT15M"] → 15 minutes before ["TRIGGER:-PT1H"] → 1 hour before ["TRIGGER:-P1D"] → 1 day before ["TRIGGER:-PT15M","TRIGGER:PT0S"] → 15 min before AND at due

Examples: # Single task with Beijing timezone, ring at due time { "title": "Buy milk", "project_id": "1234ABC", "content": "2% organic", "due_date": "2025-12-16T16:00:00+08:00", "time_zone": "Asia/Shanghai", "priority": "medium", "reminders": ["TRIGGER:PT0S"] }

# Multiple tasks (one timed, one all-day by omitting due_date)
[
    {
        "title": "Example A",
        "project_id": "1234ABC",
        "desc": "Timed task",
        "due_date": "2025-07-19T10:00:00+0000",
        "time_zone": "Asia/Shanghai",
        "priority": "high"
    },
    {
        "title": "Example B",
        "project_id": "1234XYZ",
        "content": "All-day task (no due_date means all-day)"
    }
]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses critical behaviors: the need for time_zone, the meaning of omitting due_date (all-day), the exact format for reminders (TRIGGER strings with examples), and the fact that no alarm fires without reminders. These go beyond what the schema shows.

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?

Though detailed, the description is well-organized with an opening summary, an Args list with bullet points, and two practical examples. Every clause adds value, and the most critical info (title, project_id, time_zone, reminders) is front-loaded in the Args list.

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?

For a complex tool with a single loosely-typed parameter, the description is remarkably complete: it covers all inner fields, formats, edge cases (all-day vs timed tasks), and provides examples. An output schema is present, so return values need not be described. Minor omissions like the structure of 'items' are acceptable since subtask creation is handled by a sibling tool.

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 coverage is 0%, and the schema only defines 'tasks' as an object or array. The description compensates fully by listing every inner field (title, project_id, content, desc, start_date, due_date, time_zone, priority, repeat_flag, items, reminders) with types, formats, defaults, and examples. This is exceptional compensation.

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 one or more tasks in TickTick', which is a specific verb + resource + scope. It clearly distinguishes from sibling tools like update_tasks or delete_tasks by stating creation and batch support.

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 explicitly explains when to use single vs batch creation ('For single task, you can pass a dictionary directly. For multiple tasks, pass a list of dictionaries.') and provides important usage warnings (e.g., 'Without this, NO alarm fires'). However, it does not explicitly mention alternative tools like update_tasks for modifications, but for a creation tool the usage context is 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/Code-MonkeyZhang/ticktick-mcp-enhanced'

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