Skip to main content
Glama

ticktick_create_task

Create a new task in TickTick with title, due date, priority, and reminders. Supports markdown content, subtasks, and recurrence rules.

Instructions

Create a new task.

Args: title (str): Task title. Required. project_id (str, optional): Project ID. Defaults to inbox. content (str, optional): Long-form content (markdown supported). desc (str, optional): Short description / checklist subtitle. all_day (bool, optional): True for all-day tasks. start_date (str, optional): ISO 8601 start datetime, e.g. "2026-04-13T09:00:00+01:00". due_date (str, optional): ISO 8601 due datetime. expected_day_of_week (str, optional): English weekday name. Required when due_date is set; mismatch returns an error. time_zone (str, optional): IANA timezone. Defaults to the system timezone for date conversion. reminders (list[str], optional): TickTick trigger strings, e.g. ["TRIGGER:-PT30M"]. repeat (str, optional): Recurrence rule (RFC 5545 RRULE). priority (int, optional): 0=None, 1=Low, 3=Medium, 5=High. sort_order (int, optional): Position within project. items (list[dict], optional): Subtask items.

Returns: JSON object containing the created task. If verification flags an issue, _verification_warnings is attached. Without due_date a warning is added because TickTick will not trigger a reminder. On failure: {"error": "...", "status": "error"}.

Limitations: - builder() in ticktick-py sometimes omits dates, reminders, priority and timezone; we re-populate them after the call.

Agent Usage Guide: - Always pair due_date with expected_day_of_week. - Look up a project ID with ticktick_get_all(search="projects").

Example: ticktick_create_task( title="Replace kitchen tap washer", project_id="", due_date="2026-06-01T20:45:00+01:00", expected_day_of_week="Monday", time_zone="Europe/London", priority=3, )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
project_idNo
contentNo
descNo
all_dayNo
start_dateNo
due_dateNo
expected_day_of_weekNo
time_zoneNo
remindersNo
repeatNo
priorityNo
sort_orderNo
itemsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it details return values (JSON with verification warnings, error format), limitations (builder() omissions), and edge cases (no due_date triggers a warning). This comprehensive disclosure exceeds expectations.

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 thorough and well-structured with sections (Args, Returns, Limitations, Agent Usage Guide, Example). While slightly verbose for a 14-parameter tool, each section serves a purpose. Could be trimmed slightly but remains effective.

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 tool with 14 parameters, no annotations, and an output schema, the description covers purpose, all parameters, return values (including error/warning), limitations, and usage guidance. It is fully complete for an AI agent to invoke 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?

The input schema has 0% description coverage, so the description compensates fully by providing detailed parameter descriptions, types, defaults, constraints (e.g., expected_day_of_week required with due_date), and an example call. This adds significant meaning beyond the 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 clearly states 'Create a new task.' It provides a detailed parameter list and usage guide, distinguishing it from sibling tools like ticktick_update_task and ticktick_complete_task. The purpose is unambiguous.

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 an 'Agent Usage Guide' with explicit instructions (e.g., pair due_date with expected_day_of_week, look up project ID with ticktick_get_all). It also notes limitations and provides an example, giving clear when-to-use and how-to-use guidance.

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/partymola/ticktick-mcp'

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