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.
| Parameter | Type | Description |
|---|---|---|
title | string (required) | Short title |
action_type | enum reminder | ai_task (required) | What fires: a notification or an autonomous AI run |
at | string (ISO) | One-off: the fire time. Recurring: the anchor — start date and time of day of every recurrence. Without at, a recurrence starts from now |
rrule | string | iCal RRULE, e.g. FREQ=WEEKLY;BYDAY=MO,WE,FR — allowed parts under Recurrence. Omit for a one-off task |
timezone | string | IANA timezone, e.g. Europe/Berlin. Daily or coarser recurrences keep the anchor's date and time of day in this zone (wall clock): 09:00 stays 09:00 across daylight-saving changes. Omitted or invalid → the server computes in UTC |
max_runs | integer > 0 | Stop after this many runs (recurring only). The way to limit a series by count — COUNT in the RRULE is not evaluated |
Provide at least at or rrule. With both, at is the anchor of the recurrence.
reminder only:
| Parameter | Type | Description |
|---|---|---|
message | string (required) | The notification text |
recipients | string[] | User IDs (default: yourself) |
list / list_item | string | Related list/item for the deep link |
post_to_item_chat | boolean | Additionally post permanently into the item's chat (only with list_item) |
create_event | object | Also create a Liza calendar event: title, start, end, duration_minutes (default 30), all_day, location, description, calendar |
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:
| Parameter | Type | Description |
|---|---|---|
prompt | string (required) | What the AI should do |
provider | string | AI provider (default: x-liza-provider, or the last one used for this scope) |
model | string | Model override |
scope / scope_id | string | Scope type (e.g. item) and UUID |
scope_key | string | Identifies the AI conversation. If omitted, the current conversation is used (header x-liza-conversation) |
{"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.
| Part | Values | Note |
|---|---|---|
FREQ | MINUTELY, HOURLY, DAILY, WEEKLY, MONTHLY, YEARLY | Required |
INTERVAL | positive integer | Default 1 |
BYDAY | MO … SU, comma-separated | only with FREQ=WEEKLY; no ordinals (1MO, -1FR are rejected) |
UNTIL | 20261231T235959Z, 20261231T235959, 20261231 or ISO 8601 | End of the series, inclusive. Without Z or an offset, the task's timezone applies; a plain date includes the whole day |
WKST | MO … SU | Week start for INTERVAL with BYDAY (default MO) |
COUNT | positive integer | accepted but not evaluated — the series keeps running. Set max_runs to limit it |
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
| Parameter | Type | Default | Description |
|---|---|---|---|
status | enum active | paused | done | error | canceled | all | active | Filter |
limit | number | 50 | Max results |
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
| Parameter | Type | Description |
|---|---|---|
taskId | string (required) | UUID or SID |
title | string | New title |
at | string (ISO) | New time / anchor |
rrule | string | New RRULE — an empty string makes the task one-off |
timezone | string | New timezone (wall clock as for schedule_task) |
max_runs | integer | null | Set/remove the limit |
message / recipients | string / string[] | reminder only |
prompt / provider / model | string | ai_task only |
Given fields are merged into the existing task.
pause_scheduled_task
Pause or resume. write · user
| Parameter | Type | Default | Description |
|---|---|---|---|
taskId | string (required) | – | UUID or SID |
resume | boolean | false | true = reactivate a paused task |
cancel_scheduled_task
Cancel permanently — the task will never fire again. destructive · user
| Parameter | Type | Description |
|---|---|---|
taskId | string (required) | UUID or SID |