ticktick_guide
Navigate TickTick MCP tools by category, user intent, or workflow. Use this guide to identify the correct tool for your goal.
Instructions
Interactive guide to all TickTick MCP tools — START HERE.
[Category: Utilities] [Auth: none]
[Related: check_v2_availability]
Call with no args to see all categories and tool names.
Call with a category name to see tools in that category.
Call with an intent name to see the recommended tool path for a real user goal.
Call with show_workflows=True to see common multi-step patterns.
Args:
category: Filter by category name (partial match, case-insensitive).
Examples: "task", "tag", "habit", "project", "sync", "focus".
intent: Filter by user intent, e.g. "know_what_to_do_today", "find_a_note",
"reorganize_projects", or "clean_up_tasks".
show_workflows: If True, return common multi-step workflow recipes.
Tip: Call check_v2_availability() to see which features need a session token.
Query filter ergonomics: for multi-value string filters (project/folder IDs or
names, tags, search_fields, kinds), tools accept either a single string or a list.
── AGENT OPERATING CONTRACT ─────────────────────────────────────────────────
The TickTick API is dual-layer (V1 official + V2 unofficial) with silent failure
modes. Agents MUST apply the following discipline on every interaction:
1. VERIFY AFTER EVERY WRITE: After create/update/delete operations, always call
get_task_detail() (or equivalent read tool) to confirm the server state
matches the intent. Do not trust API response codes alone — silent partial
failures are common (reminders, parentId, groupId).
2. RETRY UNTIL CONFIRMED: If verification reveals a mismatch, diagnose the root
cause (V1/V2 API duality, missing anchor field, wrong format), adjust the
call strategy, and retry. Repeat verify → fix → retry until state is correct.
3. PROACTIVE USER FEEDBACK: After completing a multi-step task or recovering
from a silent failure, report to the user:
- What was attempted and what the API actually accepted.
- Any workaround applied (e.g., switched from V2 batch to V1 update_task).
- Recommendations for future similar operations.
4. KNOWN SILENT FAILURE PATTERNS (see individual tool docs for details):
- reminder_minutes on V2-created tasks → requires explicit due_date anchor
in update_task() V1; batch_update_tasks() V2 cannot anchor reminders.
- parentId at task creation → always silently ignored; use set_subtask_parent.
- groupId at project creation → use V2 batch/project to set folder after.
- reminder object format {trigger:} → silently rejected; use update_task V1.
─────────────────────────────────────────────────────────────────────────────Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | ||
| intent | No | ||
| show_workflows | No |