delete_task
Behavior, inputs, outputs and permissions for delete_task.
Reviewed · 2026-09-20 / Ridian
This reference is generated from the published tool contract.
Behavior and boundaries
Section titled “Behavior and boundaries”Permanently deletes exactly one writable Google Tasks or Microsoft To Do task. Use list_tasks or get_task first and proceed only when exactly one intended task matches and writable=true. The account, list, task, provider grant, organization binding, and current existence are revalidated immediately before deletion. Repeating the same deletion is safe and reports changed=false.
Permissions
Section titled “Permissions”Granted scopes, accounts, calendars and visibility rules limit access. Workspace administrators do not automatically gain access to other users’ accounts.
tasks:read, tasks:write
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "accountId": { "type": "string", "minLength": 1 }, "taskListId": { "type": "string", "minLength": 1, "maxLength": 2048 }, "taskId": { "type": "string", "minLength": 1, "maxLength": 2048 } }, "required": [ "accountId", "taskListId", "taskId" ], "additionalProperties": false}Output
Section titled “Output”{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "found": { "type": "boolean", "const": true }, "changed": { "type": "boolean" } }, "required": [ "found", "changed" ], "additionalProperties": false}Errors and retries
Section titled “Errors and retries”Check the tool result for errors. Do not blindly retry writes after a timeout. Check the calendar state first.