Local-first task manager: create, edit, and complete tasks, projects, and checklists via MCP.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Add a file to a task or remove one. `action: "add"` fetches the given HTTPS `url`: the server downloads it, verifies its size and type, and stores it, so the model never sends file bytes. Pass a stable idempotency_key and reuse it for retries so a lost response cannot upload the file twice. `action: "remove"` deletes the named `attachment`. Read a task's files with task_show and `include: ["attachments"]`. Limited to 10 attachments per task and 10 MB per file. Allowed types: images (jpeg, png, gif, webp, heic), PDF, CSV, Markdown, and plain text.
Workspace-scoped task number, encoded as a string
Whether to attach a file or delete one
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."
HTTPS URL of the file to attach. Required to add
Display filename on an add; defaults to the URL's last path segment
Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices
Attachment UUID or prefix (>= 4 chars). Required to remove
Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id.
The server marks this tool as destructive. Running it may delete or overwrite data on the server or in any account you connected with your headers.
Add a file to a task or remove one. `action: "add"` fetches the given HTTPS `url`: the server downloads it, verifies its size and type, and stores it, so the model never sends file bytes. Pass a stable idempotency_key and reuse it for retries so a lost response cannot upload the file twice. `action: "remove"` deletes the named `attachment`. Read a task's files with task_show and `include: ["attachments"]`. Limited to 10 attachments per task and 10 MB per file. Allowed types: images (jpeg, png, gif, webp, heic), PDF, CSV, Markdown, and plain text.
| Argument | Type | Description |
|---|---|---|
| url | string | HTTPS URL of the file to attach. Required to add |
| task* | string | Workspace-scoped task number, encoded as a string |
| action* | string | Whether to attach a file or delete one |
| context* | string | 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." |
| filename | string | Display filename on an add; defaults to the URL's last path segment |
| workspace | string | Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices |
| attachment | string | Attachment UUID or prefix (>= 4 chars). Required to remove |
| idempotency_key | string | Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"action",
"task",
"context"
],
"properties": {
"url": {
"type": "string",
"format": "uri",
"description": "HTTPS URL of the file to attach. Required to add"
},
"task": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"action": {
"enum": [
"add",
"remove"
],
"type": "string",
"description": "Whether to attach a file or delete one"
},
"context": {
"type": "string",
"description": "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.\""
},
"filename": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Display filename on an add; defaults to the URL's last path segment"
},
"workspace": {
"type": "string",
"description": "Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"
},
"attachment": {
"type": "string",
"minLength": 4,
"description": "Attachment UUID or prefix (>= 4 chars). Required to remove"
},
"idempotency_key": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id."
}
}
}Change the checklist on a task. `action: "add"` appends items, unchecked, after the existing ones: pass every title for a multi-item list in one call (`titles` keeps the given order, while parallel single adds land in arrival order). `action: "edit"` renames an item and/or checks it (`completed: true`) or unchecks it (`completed: false`). `action: "remove"` deletes one. Read the list, with each item's id and state, from task_show.
| Argument | Type | Description |
|---|---|---|
| item | string | Checklist item UUID or prefix (>= 4 chars). Required to edit or remove |
| task* | string | Workspace-scoped task number, encoded as a string |
| title | string | One item title to add, or the new title on an edit |
| action* | string | What to do to the checklist |
| titles | array | Several item titles to add, kept in the given order (use instead of `title`) |
| context* | string | 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." |
Write on a task's comment thread. `action: "add"` posts a comment, attributed to the connected user and visible to everyone in the workspace, so write it as a message to the user's teammates rather than a note to the user; nobody is notified. `action: "edit"` rewrites one of your own (only its author may, and it is then marked edited). `action: "remove"` deletes one permanently — comments have no Trash — so confirm with the user first. Read the thread with task_show and `include: ["comments"]`.
| Argument | Type | Description |
|---|---|---|
| body | string | Comment text. Required to add or edit |
| task* | string | Workspace-scoped task number, encoded as a string |
| action* | string | What to do on the thread |
| comment | string | Comment UUID or prefix (>= 4 chars). Required to edit or remove |
| context* | string | 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." |
Get a snapshot of the current workspace: task counts per view, recent open tasks, and every project, label, team and member. This is the tool that answers what is in the workspace and resolves a project, label, team or member by name — there is no separate list tool for those. Use it for that, not as a warm-up before every turn. For tasks themselves use task_list (a view), search (by words) or task_show (one task): the recent tasks here are only the latest few.
| Argument | Type | Description |
|---|---|---|
| context* | string | 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." |
| timezone | string | 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. |
| workspace | string | Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices |
| tasks_limit | integer | Max recent open tasks to return |
Read Done Bear's guide for one topic: what the data means, how it relates to the rest of the product, and how to use it well. Load a topic before doing that kind of work for the first time in a session. - `views`: Placing a task in Inbox/Today/Upcoming/Anytime/Someday, reading a view, or working out why Today looks wrong. - `dates`: Setting or clearing a due date, or deciding between a deadline and a start date. - `editing`: Changing a task's fields, clearing a value, appending to notes, or moving a task between projects. - `bulk`: Completing, moving, or editing more than one task at a time, or sweeping a whole view. - `checklists`: Adding sub-steps to a task, building a list inside a task, or ticking items off. - `comments`: Discussing a task with teammates: reading its thread, replying, or correcting a comment. - `projects`: Deciding where a task belongs, creating a project or label, changing a project's status, or joining/leaving a project. - `search`: Looking a task up, listing a view, paging through results, or orienting in a new workspace. - `workspaces`: Working across multiple workspaces, hitting a permission or rate-limit error, or making retries safe. - `agents`: Starting work in a Done Bear workspace for the first time. - `importing`: The user asks how to move their tasks in from Todoist, Things, Trello or a CSV.
| Argument | Type | Description |
|---|---|---|
| topic* | string | Guide topic to read |
| context* | string | 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." |
Create a new label in the workspace and return its id. Only creates the label: to put it on a task, pass it to task_add `labels` or task_edit `add_labels` afterwards (both take the title). Titles are not unique, so a second call with the same title makes a duplicate — check the labels get_context returns first, and reuse one that already exists.
| Argument | Type | Description |
|---|---|---|
| title* | string | Label title |
| context* | string | 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." |
| workspace | string | 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 | string | Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"title",
"context"
],
"properties": {
"title": {
"type": "string",
"maxLength": 255,
"minLength": 1,
"description": "Label title"
},
"context": {
"type": "string",
"description": "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.\""
},
"workspace": {
"type": "string",
"description": "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": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id."
}
}
}Create or change a project. `action: "add"` creates one (name required). `action: "edit"` updates the named project: only the fields given change, and an empty string clears description or target_date. `action: "join"` puts it in the caller's Your projects sidebar list and `action: "leave"` takes it out. Read projects with get_context.
| Argument | Type | Description |
|---|---|---|
| name | string | Project name. Required on add; a rename on edit |
| action* | string | What to do with the project |
| status | string | Project status (edit only) |
| context* | string | 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 | string | Project id, key, or name. Required for edit, join and leave |
| workspace | string | Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices |
Search tasks across the workspace. Ranked lexical search over title and description: exact and prefix matches rank first, then word-boundary, substring, and fuzzy matches, with recency and status factored in. Multi-word queries match in any order. Searches every state by default, completed and archived included. Use this when the user names a task by its words; use task_list to browse a view (Today, Inbox, …) and task_show once you have the task number.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results |
| query* | string | Search query (matches title and description) |
| state | string | Filter by task state |
| cursor | string | Opaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page. |
| context* | string | 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." |
| timezone |
Create 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.
| Argument | Type | Description |
|---|---|---|
| team | string | Team id, key, or name |
| when | string | 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 | string | Task description/notes |
| title* | string | Task title |
| labels | array | Labels to attach (each a label id, title, or id prefix) |
| context |
Read the task-agent identity bound to this connection's existing API key in one explicit workspace. Returns only key metadata and the exact agent UUID or null; an inactive agent includes disabledAt. Requires an API-key connection and current workspace membership. Does not register, assign or start any task. Use this before task_agent_register and retain key.id as expected_key_id.
| Argument | Type | Description |
|---|---|---|
| context* | string | 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." |
| workspace_id* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"workspace_id",
"context"
],
"properties": {
"context": {
"type": "string",
"description": "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.\""
},
"workspace_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
}
}
}Explicitly register one assignable task agent for this connection's existing key in one workspace, after the user approves that durable binding. Requires a write-scoped API key restricted to exactly this workspace and an owner/admin membership. Read task_agent_get first and pass its key.id as expected_key_id. Same key/workspace/name retries return the same UUID; conflicting or inactive bindings fail without takeover or reactivation. Creates no key, changes no scope, and does not assign/import/start tasks.
| Argument | Type | Description |
|---|---|---|
| name* | string | |
| context* | string | 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." |
| workspace_id* | string | |
| expected_key_id* | string |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"expected_key_id",
"name",
"workspace_id",
"context"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1
},
"context": {
"type": "string",
"description": "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.\""
},
"workspace_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
},
"expected_key_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
}
}
}Archive a task, or several at once with `tasks` (max 50). They move to the Trash view, out of every working list, and stay readable there (task_list `view: "trash"`). Archiving is not completing: use task_done for work that was finished, and task_archive only for tasks the user wants gone. Confirm with the user first.
| Argument | Type | Description |
|---|---|---|
| task | string | Workspace-scoped task number, encoded as a string |
| tasks | array | Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it. |
| context* | string | 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." |
| workspace | string | Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"context"
],
"properties": {
"task": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"tasks": {
"type": "array",
"items": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"maxItems": 50,
"minItems": 1,
"description": "Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it."
},
"context": {
"type": "string",
"description": "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.\""
},
"workspace": {
"type": "string",
"description": "Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"
}
}
}Mark a task as complete, or several at once with `tasks` (max 50). They move to the Logbook view. A set of 50 is undone one task_reopen call at a time, so confirm the list with the user first.
| Argument | Type | Description |
|---|---|---|
| task | string | Workspace-scoped task number, encoded as a string |
| tasks | array | Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it. |
| context* | string | 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." |
| workspace | string | Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices |
| expectedRevision | integer | Complete only the reviewed task revision from task_show or task_list. Use with task, not tasks. A changed task returns a conflict; reload and review before trying again. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"context"
],
"properties": {
"task": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"tasks": {
"type": "array",
"items": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"maxItems": 50,
"minItems": 1,
"description": "Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it."
},
"context": {
"type": "string",
"description": "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.\""
},
"workspace": {
"type": "string",
"description": "Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"
},
"expectedRevision": {
"type": "integer",
"maximum": 9007199254740991,
"description": "Complete only the reviewed task revision from task_show or task_list. Use with task, not tasks. A changed task returns a conflict; reload and review before trying again.",
"exclusiveMinimum": 0
}
}
}Update fields on one task (`task`) or on several at once (`tasks`, max 50). Only the provided fields are changed; omitted fields are left untouched. To remove a value, list the field in `clear` (e.g. `clear: ["deadline"]`). Notes replace the existing notes (no append). `assignee` assigns the task; clear it to unassign. `add_labels` and `remove_labels` change which labels are on it. Editing several tasks applies the same changes to every one of them and cannot be undone in one call, so confirm the list with the user first. For status changes use task_done, task_reopen or task_archive, and for checklist items use the available checklist tools; this tool does not change either.
| Argument | Type | Description |
|---|---|---|
| task | string | Workspace-scoped task number, encoded as a string |
| team | string | Team id, key, or name |
| when | string | Move to a different GTD view |
| clear | array | Fields to remove a value from, e.g. ["deadline"]. Use this rather than sending an empty string. |
| notes | string | New description/notes (replaces existing) |
| tasks | array | Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it. |
| title |
List tasks in the workspace, most recently updated first. Completed tasks are ordered by completion time, newest first. Filter by view (inbox, today, upcoming, anytime, someday, logbook, trash) and/or state (open, done, archived, all); `search` ranks matches within that filter. `view: "logbook"` reads completed tasks and `view: "trash"` archived ones, whatever `state` says. Returns up to `limit` tasks; `hasMore` is true when more matched than were returned, and passing `nextCursor` back as `cursor` reads the next page. To find a task by its words across every view use search instead, and task_show for one task's checklist, comments and files.
| Argument | Type | Description |
|---|---|---|
| view | string | Filter by GTD view bucket. logbook and trash read the completed and archived tasks regardless of `state` |
| limit | integer | Max results |
| state | string | Filter by task state |
| cursor | string | Opaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page. |
| search | string | Ranked lexical search over title/description; when set, results are ordered by relevance instead of recency |
| context* | string | 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." |
Reopen a completed task, or several at once with `tasks` (max 50). Each returns to its previous view.
| Argument | Type | Description |
|---|---|---|
| task | string | Workspace-scoped task number, encoded as a string |
| tasks | array | Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it. |
| context* | string | 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." |
| workspace | string | Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"context"
],
"properties": {
"task": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"tasks": {
"type": "array",
"items": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"maxItems": 50,
"minItems": 1,
"description": "Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it."
},
"context": {
"type": "string",
"description": "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.\""
},
"workspace": {
"type": "string",
"description": "Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"
}
}
}Get full details for a single task: its fields, labels and checklist items, by workspace-scoped task number. Add `include` for the parts that cost extra reads: `["comments"]` for the discussion thread (oldest first, with author and whether each was edited) and `["attachments"]` for the files on it, each with a short-lived signed URL.
| Argument | Type | Description |
|---|---|---|
| task* | string | Workspace-scoped task number, encoded as a string |
| context* | string | 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." |
| include | array | Extra sections to load. Omit unless you need them: each is its own round trip |
| timezone | string | 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. |
| workspace | string | Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices |
| completed | boolean | Check (true) or uncheck (false) the item, on an edit |
| workspace | string | 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 | string | Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"action",
"task",
"context"
],
"properties": {
"item": {
"type": "string",
"minLength": 4,
"description": "Checklist item UUID or prefix (>= 4 chars). Required to edit or remove"
},
"task": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"title": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "One item title to add, or the new title on an edit"
},
"action": {
"enum": [
"add",
"edit",
"remove"
],
"type": "string",
"description": "What to do to the checklist"
},
"titles": {
"type": "array",
"items": {
"type": "string",
"maxLength": 500,
"minLength": 1
},
"maxItems": 100,
"minItems": 1,
"description": "Several item titles to add, kept in the given order (use instead of `title`)"
},
"context": {
"type": "string",
"description": "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.\""
},
"completed": {
"type": "boolean",
"description": "Check (true) or uncheck (false) the item, on an edit"
},
"workspace": {
"type": "string",
"description": "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": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id."
}
}
}| workspace |
| string |
| 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 | string | Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"action",
"task",
"context"
],
"properties": {
"body": {
"type": "string",
"maxLength": 10000,
"minLength": 1,
"description": "Comment text. Required to add or edit"
},
"task": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"action": {
"enum": [
"add",
"edit",
"remove"
],
"type": "string",
"description": "What to do on the thread"
},
"comment": {
"type": "string",
"minLength": 4,
"description": "Comment UUID or prefix (>= 4 chars). Required to edit or remove"
},
"context": {
"type": "string",
"description": "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.\""
},
"workspace": {
"type": "string",
"description": "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": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id."
}
}
}| projects_status |
| string |
| Which projects to return |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"context"
],
"properties": {
"context": {
"type": "string",
"description": "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.\""
},
"timezone": {
"type": "string",
"description": "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."
},
"workspace": {
"type": "string",
"description": "Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"
},
"tasks_limit": {
"type": "integer",
"default": 10,
"maximum": 50,
"minimum": 1,
"description": "Max recent open tasks to return"
},
"projects_status": {
"enum": [
"active",
"done",
"archived",
"all"
],
"type": "string",
"default": "active",
"description": "Which projects to return"
}
}
}{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"topic",
"context"
],
"properties": {
"topic": {
"enum": [
"views",
"dates",
"editing",
"bulk",
"checklists",
"comments",
"projects",
"search",
"workspaces",
"agents",
"importing"
],
"type": "string",
"description": "Guide topic to read"
},
"context": {
"type": "string",
"description": "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.\""
}
}
}| description | string | Project description (empty string clears it on an edit) |
| target_date | string | Target date (YYYY-MM-DD), or an empty string to clear it (edit only) |
| idempotency_key | string | Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"action",
"context"
],
"properties": {
"name": {
"type": "string",
"minLength": 1,
"description": "Project name. Required on add; a rename on edit"
},
"action": {
"enum": [
"add",
"edit",
"join",
"leave"
],
"type": "string",
"description": "What to do with the project"
},
"status": {
"enum": [
"active",
"on_hold",
"done",
"cancelled"
],
"type": "string",
"description": "Project status (edit only)"
},
"context": {
"type": "string",
"description": "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": {
"type": "string",
"minLength": 1,
"description": "Project id, key, or name. Required for edit, join and leave"
},
"workspace": {
"type": "string",
"description": "Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"
},
"description": {
"type": "string",
"description": "Project description (empty string clears it on an edit)"
},
"target_date": {
"type": "string",
"description": "Target date (YYYY-MM-DD), or an empty string to clear it (edit only)"
},
"idempotency_key": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id."
}
}
}| string |
| 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. |
| workspace | string | Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query",
"context"
],
"properties": {
"limit": {
"type": "integer",
"default": 20,
"maximum": 100,
"minimum": 1,
"description": "Max results"
},
"query": {
"type": "string",
"minLength": 1,
"description": "Search query (matches title and description)"
},
"state": {
"enum": [
"open",
"done",
"archived",
"all"
],
"type": "string",
"default": "all",
"description": "Filter by task state"
},
"cursor": {
"type": "string",
"description": "Opaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page."
},
"context": {
"type": "string",
"description": "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.\""
},
"timezone": {
"type": "string",
"description": "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."
},
"workspace": {
"type": "string",
"description": "Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"
}
}
}| string |
| 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 | string | Project id, key, or name to assign this task to |
| assignee | string | Member (user id, name, or email) or task agent (id or name) to assign the task to |
| deadline | string | Due date in YYYY-MM-DD format |
| timezone | string | 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 | array | Checklist item titles to create on the task, kept in the given order |
| workspace | string | 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 | string | Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"title",
"context"
],
"properties": {
"team": {
"type": "string",
"description": "Team id, key, or name"
},
"when": {
"enum": [
"inbox",
"anytime",
"today",
"upcoming",
"someday"
],
"type": "string",
"description": "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": {
"type": "string",
"description": "Task description/notes"
},
"title": {
"type": "string",
"minLength": 1,
"description": "Task title"
},
"labels": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"description": "Labels to attach (each a label id, title, or id prefix)"
},
"context": {
"type": "string",
"description": "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": {
"type": "string",
"description": "Project id, key, or name to assign this task to"
},
"assignee": {
"type": "string",
"description": "Member (user id, name, or email) or task agent (id or name) to assign the task to"
},
"deadline": {
"type": "string",
"description": "Due date in YYYY-MM-DD format"
},
"timezone": {
"type": "string",
"description": "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": {
"type": "array",
"items": {
"type": "string",
"maxLength": 500,
"minLength": 1
},
"maxItems": 100,
"description": "Checklist item titles to create on the task, kept in the given order"
},
"workspace": {
"type": "string",
"description": "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": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "Stable key that makes retries safe: repeated calls with the same key create only one record and return the same id."
}
}
}| string |
| New title |
| context* | string | 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 | string | Project id, key, or name |
| assignee | string | Assign to a member (user id, name, or email) or a task agent (id or name) |
| deadline | string | Set due date (YYYY-MM-DD) |
| timezone | string | 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. |
| workspace | string | Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices |
| add_labels | array | Labels to attach (each a label id, title, or id prefix). The label has to exist already — create one with label_create |
| remove_labels | array | Labels to detach (each a label id, title, or id prefix) |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"context"
],
"properties": {
"task": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"team": {
"type": "string",
"description": "Team id, key, or name"
},
"when": {
"enum": [
"inbox",
"anytime",
"today",
"upcoming",
"someday"
],
"type": "string",
"description": "Move to a different GTD view"
},
"clear": {
"type": "array",
"items": {
"enum": [
"deadline",
"project",
"team",
"assignee",
"notes"
],
"type": "string"
},
"description": "Fields to remove a value from, e.g. [\"deadline\"]. Use this rather than sending an empty string."
},
"notes": {
"type": "string",
"description": "New description/notes (replaces existing)"
},
"tasks": {
"type": "array",
"items": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"maxItems": 50,
"minItems": 1,
"description": "Several workspace-scoped task numbers (max 50), instead of `task`. Confirm the list with the user first: one call changes every task in it."
},
"title": {
"type": "string",
"description": "New title"
},
"context": {
"type": "string",
"description": "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": {
"type": "string",
"description": "Project id, key, or name"
},
"assignee": {
"type": "string",
"description": "Assign to a member (user id, name, or email) or a task agent (id or name)"
},
"deadline": {
"type": "string",
"description": "Set due date (YYYY-MM-DD)"
},
"timezone": {
"type": "string",
"description": "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."
},
"workspace": {
"type": "string",
"description": "Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"
},
"add_labels": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"description": "Labels to attach (each a label id, title, or id prefix). The label has to exist already — create one with label_create"
},
"remove_labels": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"description": "Labels to detach (each a label id, title, or id prefix)"
}
}
}| timezone | string | 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. |
| workspace | string | Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"context"
],
"properties": {
"view": {
"enum": [
"inbox",
"anytime",
"today",
"upcoming",
"someday",
"logbook",
"trash"
],
"type": "string",
"description": "Filter by GTD view bucket. logbook and trash read the completed and archived tasks regardless of `state`"
},
"limit": {
"type": "integer",
"default": 20,
"maximum": 100,
"minimum": 1,
"description": "Max results"
},
"state": {
"enum": [
"open",
"done",
"archived",
"all"
],
"type": "string",
"default": "open",
"description": "Filter by task state"
},
"cursor": {
"type": "string",
"description": "Opaque pagination cursor from a previous call's `nextCursor`. Pass it with the same filters to fetch the next page."
},
"search": {
"type": "string",
"description": "Ranked lexical search over title/description; when set, results are ordered by relevance instead of recency"
},
"context": {
"type": "string",
"description": "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.\""
},
"timezone": {
"type": "string",
"description": "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."
},
"workspace": {
"type": "string",
"description": "Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"
}
}
}{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"task",
"context"
],
"properties": {
"task": {
"type": "string",
"pattern": "^[1-9]\\d*$",
"description": "Workspace-scoped task number, encoded as a string"
},
"context": {
"type": "string",
"description": "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.\""
},
"include": {
"type": "array",
"items": {
"enum": [
"comments",
"attachments"
],
"type": "string"
},
"description": "Extra sections to load. Omit unless you need them: each is its own round trip"
},
"timezone": {
"type": "string",
"description": "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."
},
"workspace": {
"type": "string",
"description": "Workspace id, slug, or name. Required when the account has more than one workspace: a call without it then fails and names the choices"
}
}
}