Appearance
Tasks
To-dos and follow-ups, including batched and idempotent writes.
11 tools — 3 read, 8 write.
| Tool | What it does | |
|---|---|---|
add_task_dependency | write | Add a dependency between two tasks: taskId blocks blockedById (so blockedById is blocked by taskId). |
complete_task | write | Mark a task as done. |
create_subtask | write | Create a subtask under a parent task. |
create_task | write | Create a new task (action item). |
list_task_tags | read | List all distinct tags used on tasks in the org. |
list_tasks | read | List tasks in the org, optionally filtered by state, owner, priority, due range, or tags. |
remove_task_dependency | write | Remove a dependency between two tasks (the taskId → blockedById blocking edge). |
search_tasks | read | Search existing tasks by keyword (matches title, description, and tags, case-insensitive). |
set_task_parent | write | Set (or clear) a task's parent. |
update_task | write | Patch a task. |
upsert_tasks | write | Create many tasks in ONE call (max 500), idempotently. |
Calling these
Over MCP, find one with search_tools, then run it with execute_tool. Over REST, POST /api/capabilities/<tool> with the arguments as the JSON body. Either way, fetch the input schema for the tool you're about to call rather than guessing — get_tool_schema over MCP, or GET /api/capabilities?name=<tool> over REST.
See How the API works for auth, errors and the shared envelope.