Skip to main content
Glama

update_task

Update any field of an existing TickTick task, including title, content, priority, due date, tags, and status, with partial updates.

Instructions

Update any fields of an existing task. Only provided fields are changed
(read-modify-write under the hood — safe for partial updates).

[Category: Tasks — Write]  [Auth: V1]
[Related: get_task_detail, create_task, complete_task, reopen_task]

Args:
    task_id: The task to update.
    project_id: The project containing the task (required by API).
    title: New title.
    content: New body/description.
    desc: Alt description field.
    priority: 0=none, 1=low, 3=medium, 5=high.
    due_date: ISO 8601. Pass "" to clear.
    start_date: ISO 8601. Pass "" to clear.
    time_zone: IANA timezone.
    tags: Full replacement list. Pass [] to clear all tags.
    status: 0=active, 2=completed, -1=abandoned (V2).
    all_day: True/False.
    column_id: Move to a kanban column.
    reminder_minutes: List of minutes-before. Pass [] to clear reminders.
        ⚠️ V1/V2 GOTCHA — REMINDER ANCHOR REQUIRED:
        Tasks created via V2 batch may have dueDate invisible to V1 (returns null).
        V1 uses dueDate as the anchor to compute reminder trigger offsets (TRIGGER:-P2D).
        If due_date is null, reminder_minutes is silently ignored — no error, no reminder.
        FIX: ALWAYS pass due_date + time_zone explicitly alongside reminder_minutes,
        even if you are not changing the due date. Read the existing due date from
        get_task_detail() first, then pass it through. Example:
            update_task(task_id='...', project_id='...', due_date='2026-06-03T21:00:00+0000',
                        time_zone='Europe/Paris', reminder_minutes=[2880, 1440])
        Returns reminders: ['TRIGGER:-P2D', 'TRIGGER:-P1D'] when correctly anchored.
    recurrence: RRULE string (use build_recurrence_rule). Pass "" to clear.
    progress: 0-100 percentage (V2).
    sort_order: Custom sort order.
    kind: "TEXT", "NOTE", or "CHECKLIST".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
project_idYes
titleNo
contentNo
descNo
priorityNo
due_dateNo
start_dateNo
time_zoneNo
tagsNo
statusNo
all_dayNo
column_idNo
reminder_minutesNo
recurrenceNo
progressNo
sort_orderNo
kindNo
Behavior5/5

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

Despite no annotations, the description fully discloses behavioral traits: read-modify-write (safe for partial updates), reminder anchor dependency, silent failure when due_date is null, and the need to pass unchanged fields for correct reminder computation. The V1/V2 gotcha is explained in detail.

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 long but well-structured with clear sections (Args, Category, Auth, Related). The gotcha is verbose but necessary. It front-loads the main action and then details parameters. Minor improvement: could be slightly more compact.

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 18 parameters, no output schema, and no annotations, the description covers all necessary context: parameter behaviors, usage constraints, gotchas, and examples. It provides everything an agent needs to invoke the 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?

With 0% schema description coverage, the description compensates completely. Every parameter (priority values, date clearing, tag replacement, status codes, recurrence, etc.) is explained. The reminder_minutes parameter includes critical usage context and an example.

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 explicitly states 'Update any fields of an existing task', clearly identifies the resource and action. It distinguishes from siblings like create_task, complete_task, reopen_task through the 'Related' section and the main verb 'update'.

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 provides explicit when-to-use guidance by referencing related tools (get_task_detail, create_task, etc.) and includes a detailed gotcha about reminders requiring due_date+time_zone. It gives an example and conditions for correct usage.

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