Skip to main content
Glama

update_task

Update selected fields on an existing TickTick task while leaving omitted fields unchanged; complete or move tasks via their dedicated actions.

Instructions

Update fields on an existing TickTick task. Omitted fields stay unchanged. Use complete_task to mark it done or move_tasks to move it.

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": {
      "projectId": "<projectId>",
      "taskId": "<taskId>"
    },
    "name": "update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNo
tagsNoReplace the task tags with this list. Use [] or null to clear them.
itemsNoChecklist subtasks. Send the complete list when updating.
titleNo
taskIdYesTickTick task ID.
contentNo
dueDateNoNew due date/time; null clears it.
isAllDayNo
parentIdNoMove under this parent task; null removes the parent.
priorityNoTickTick priority: 0/none, 1/low, 3/medium, 5/high.
timeZoneNo
projectIdYesCurrent TickTick project ID.
remindersNoTickTick reminder triggers such as "TRIGGER:PT0S" or "TRIGGER:P0DT9H0M0S".
sortOrderNo
startDateNoNew start date/time; null clears it.
repeatFlagNo
repeatFromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already say the tool is not read-only and not destructive, and the description adds the important partial-update behavior that omitted fields stay unchanged. However, it does not disclose that list fields such as tags and subtasks are replaced rather than merged, nor does it explain null-clearing behavior beyond what the schema states.

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?

The description is three sentences and front-loads the core update behavior before the alternatives. There is no redundant or wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 17-parameter update tool with no output schema, the description is too thin to fully orient an agent. It omits important update semantics such as replacing tags and subtasks, clearing fields with null, and the parentId movement behavior that appears in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds only the general partial-update rule that omitted fields are unchanged. With 17 parameters and only moderate schema description coverage, it does not compensate for undocumented parameters or clarify required IDs, null clearing, list replacement, priority formats, or reminders.

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 states a specific verb and resource: update fields on an existing TickTick task. It also distinguishes the tool from complete_task and move_tasks, so an agent can identify its purpose without opening the schema.

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 explicit alternatives for marking a task done and moving a task, which is useful routing guidance. It does not fully define when to use update_task versus create_task or delete_task, but the update-only scope makes that distinction fairly clear.

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