Tasks

Fetch one task by its ID. Requires a real taskId, never invent IDs; use tasks_queryTasks first when the ID is unknown.

List calendar occurrences for open, calendar-visible tasks with due dates inside a datetime range. The range must be valid and under 93 days.

Search or filter tasks by free text, view (all, inbox, today, upcoming, overdue, completed), status, priority, tag, or projectId. Use view 'today' or 'overdue' with a small limit for daily planning. Supports a due-date range, ALWAYS pass dueFrom/dueTo when the question concerns a period (a week, a month, 'soon'); the range targets open, dated tasks. Rows are compact summaries; use tasks_getTask (or detail 'full') when the user needs full notes or checklist.

Count tasks by status plus how many open tasks are overdue. Prefer this over tasks_queryTasks for how-many questions.

No input.

Create one actionable task. Preserve the user's dueDate (YYYY-MM-DD), dueTime (HH:mm), priority, projectName or list, area, tags, notes, checklist, recurrence, and reminder offsets. Example: title 'Buy groceries', dueDate 2026-07-02, dueTime 18:00, projectName 'Home', tags ['errand'], reminderOffsetsMinutes [60].

{
  "task": {
    "title": "Renew passport",
    "dueDate": "2026-10-15",
    "priority": "high"
  }
}

Apply ONE change to every task matching a filter, in a single call, for example moving all overdue tasks to a new due date. The filter runs in Vritto, so you never list or patch the tasks yourself. Returns a count and a small sample, not the rows. Tell the user what will change before you run it.

Note: Applies one change to every task matching the filter, up to 100.

{
  "filter": {
    "view": "overdue"
  },
  "patch": {
    "dueDate": "2026-09-28"
  }
}

Complete a task with recurrence awareness: the task is marked done and, if it recurs, the next occurrence is created automatically. Use tasks_setTaskStatus for ordinary non-recurring completion.

Note: Recurring tasks create their next occurrence.

Apply a partial update to one task; only the fields present in patch change. Resolve the task with tasks_queryTasks first.

{
  "taskId": "task_passport",
  "patch": {
    "dueDate": "2026-10-20"
  }
}

Set one task's status (todo, in_progress, done, cancelled). Use this for ordinary checkbox-style completion. Resolve the task with tasks_queryTasks first.

Delete (archive and cancel) one task. Only for explicit deletion requests. Resolve the task with tasks_queryTasks first.

List the user's Tasks lists (id, name) so a task can be filed by listId. Call this before setting listId.

Create one Tasks list. Only when the user asks for a new list; otherwise file into an existing one.

{
  "name": "Errands"
}

Rename or recolour one Tasks list; only the fields present change.

Archive one Tasks list. Its tasks are kept and become unsorted unless moveToListId is given.