Add Task
task_addCreate a new task. An explicit when selects its start placement: today, inbox, upcoming, anytime, or someday; upcoming schedules tomorrow. Without when, a deadline or omitted timezone selects anytime first. Otherwise, a project or team selects inbox; an unfiled task selects today. Pass the user's known IANA timezone to resolve calendar days. Use when: "inbox" for capture without a commitment to today. deadline uses YYYY-MM-DD. Optionally assign the task, attach existing labels, or pass checklist item titles in checklist; their order is preserved. The result's view reports the selected start placement, while a due or overdue deadline can make the task appear in Today. To change an existing task, use task_edit for fields or the available checklist tools for items. Search first when the user may be describing an existing task.
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": {
"title": "<title>",
"context": "<context>"
},
"name": "task_add"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| team | No | Team id, key, or name | |
| when | No | GTD view bucket: today, inbox, upcoming, anytime, someday. Omitting this means today, with three exceptions: a deadline or a missing timezone falls back to anytime (the work is due later, or today cannot be resolved), and a project or team falls back to inbox (the task is already filed). Pass timezone to get today. Use "inbox" for a capture the user has not committed to doing. | |
| notes | No | Task description/notes | |
| title | Yes | Task title | |
| labels | No | Labels to attach (each a label id, title, or id prefix) | |
| context | Yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization." | |
| project | No | Project id, key, or name to assign this task to | |
| assignee | No | Member (user id, name, or email) or task agent (id or name) to assign the task to | |
| deadline | No | Due date in YYYY-MM-DD format | |
| timezone | No | IANA timezone used to resolve "today" for views and scheduling (e.g. Australia/Melbourne). Defaults to UTC, which misclassifies Today/Upcoming for users in other timezones, so always pass the user's timezone when known. | |
| checklist | No | Checklist item titles to create on the task, kept in the given order | |
| workspace | No | Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices | |
| idempotency_key | No | Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| ok | Yes | ||
| view | Yes | ||
| title | Yes | ||
| number | Yes | ||
| checklistCount | Yes |