ticktick_complete_task
Mark a TickTick task as completed by ID and record it as processed, so it won't reappear in the unprocessed completions queue.
Instructions
Mark a task as completed.
Completing a task here also records it as processed, so it does not come
back from ticktick_get_unprocessed_completions. That queue is for
completions made elsewhere, where a note may be waiting to be read.
There is no need to call ticktick_mark_completion_processed
afterwards.
Args: task_id (str): The task's full ID.
Returns:
JSON object containing the refetched task (status=2 on success).
_verification_warnings is attached if the refetch shows the
task is still open.
completion_recorded reports whether the local record was
written. Present only when a non-recurring task completed; absent
wherever nothing was recorded, which is every recurring completion
and outcome: "uncertain". The task is complete either way.
Missing task: {"status": "not_found", "error": "..."}.
Other failures: {"error": "...", "status": "error"}.
Limitations:
- Once completed, the content field becomes immutable.
Update content with resolution notes BEFORE calling this tool.
- A recurring task's completion is never recorded, whatever the
outcome: completing one files the completed instance under an id
this tool never sees. That instance reaches the unprocessed queue.
Do not mark the series id processed by hand instead; it is not the
id the queue is showing.
Example: ticktick_complete_task(task_id="60ca9dbc8f08516d9dd56324")
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |