MCP tools: Scheduled tasks
Last updated 10 days ago
MCP tools: Scheduled tasks
Time-triggered reminders and autonomous AI runs. Functionally the same as the Schedule area in the client (see guide).
schedule_task
Schedules a task – one-off or recurring. write · user
The only scheduler for Liza: it alone is wired into the calendar, items, notifications and autonomous AI runs.
Provide at least at or rrule. With both, at is the anchor of the recurrence.
reminder only:
A reminder for a finished task is dropped
If a reminder refers to a task via list_item, the server checks the task before firing. If it is done (done, completed, closed), archived, in the trash or deleted, the reminder is cancelled instead of sent: status canceled, and a recurring reminder ends as well. If the task cannot be read at that moment, the reminder fires as usual.
ai_task only:
{"name":"schedule_task", "arguments":{"title":"Weekly report","action_type":"reminder", "rrule":"FREQ=WEEKLY;BYDAY=MO","at":"2026-09-01T07:00:00Z", "message":"Write the weekly report", "create_event":{"duration_minutes":30}}}Recurrence
rrule understands a subset of iCal (RFC 5545). The server checks strictly: a part it does not know is rejected, not silently ignored.
Everything else (BYHOUR, BYMINUTE, BYMONTHDAY, …) is rejected; the time of day comes from at. An ai_task runs at most every 15 minutes.
How the server computes:
- Wall clock:
DAILYand coarser compute in the zone fromtimezone. If the time does not exist on a day (spring, 02:30), it is moved forward by the gap (03:30); if it exists twice (autumn), the first occurrence counts. An occurrence is never skipped.MINUTELYandHOURLYrun at fixed intervals of real time. - Months and years always count from the anchor: 31 Jan → 28/29 Feb → 31 Mar → 30 Apr; 29 Feb yearly becomes 28 Feb in non-leap years.
- Weeks with
INTERVALandBYDAYcount fromWKST, not from the anchor: the anchor's week is week 0. Every 2 weeks Mon/Wed with anchor Wed 4 Nov 2026 gives Wed 4 Nov, Mon 16 Nov, Wed 18 Nov — not Mon 9 Nov.
list_scheduled_tasks
Your scheduled tasks, soonest next run first. read · follower
Per task: id, sid, title, action_type, schedule_kind (once/rrule), run_at, rrule, timezone, next_run, last_run, status, run_count, max_runs, payload, last_error.
update_scheduled_task
Rename, reschedule or change effect fields. write · user
Given fields are merged into the existing task.
pause_scheduled_task
Pause or resume. write · user
cancel_scheduled_task
Cancel permanently — the task will never fire again. destructive · user
Was this helpful?
Still need help? Ask the team