Skip to content

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.

ParameterTypeDescription
titlestring (required)Short title
action_typeenum reminder | ai_task (required)What fires: a notification or an autonomous AI run
atstring (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
rrulestringiCal RRULE, e.g. FREQ=WEEKLY;BYDAY=MO,WE,FR — allowed parts under Recurrence. Omit for a one-off task
timezonestringIANA 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_runsinteger > 0Stop 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:

ParameterTypeDescription
messagestring (required)The notification text
recipientsstring[]User IDs (default: yourself)
list / list_itemstringRelated list/item for the deep link
post_to_item_chatbooleanAdditionally post permanently into the item's chat (only with list_item)
create_eventobjectAlso 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:

ParameterTypeDescription
promptstring (required)What the AI should do
providerstringAI provider (default: x-liza-provider, or the last one used for this scope)
modelstringModel override
scope / scope_idstringScope type (e.g. item) and UUID
scope_keystringIdentifies the AI conversation. If omitted, the current conversation is used (header x-liza-conversation)
json
{"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.

PartValuesNote
FREQMINUTELY, HOURLY, DAILY, WEEKLY, MONTHLY, YEARLYRequired
INTERVALpositive integerDefault 1
BYDAYMO … SU, comma-separatedonly with FREQ=WEEKLY; no ordinals (1MO, -1FR are rejected)
UNTIL20261231T235959Z, 20261231T235959, 20261231 or ISO 8601End of the series, inclusive. Without Z or an offset, the task's timezone applies; a plain date includes the whole day
WKSTMO … SUWeek start for INTERVAL with BYDAY (default MO)
COUNTpositive integeraccepted 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: DAILY and coarser compute in the zone from timezone. 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. MINUTELY and HOURLY run 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 INTERVAL and BYDAY count from WKST, 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

ParameterTypeDefaultDescription
statusenum active | paused | done | error | canceled | allactiveFilter
limitnumber50Max 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

ParameterTypeDescription
taskIdstring (required)UUID or SID
titlestringNew title
atstring (ISO)New time / anchor
rrulestringNew RRULE — an empty string makes the task one-off
timezonestringNew timezone (wall clock as for schedule_task)
max_runsinteger | nullSet/remove the limit
message / recipientsstring / string[]reminder only
prompt / provider / modelstringai_task only

Given fields are merged into the existing task.

pause_scheduled_task ​

Pause or resume. write · user

ParameterTypeDefaultDescription
taskIdstring (required)–UUID or SID
resumebooleanfalsetrue = reactivate a paused task

cancel_scheduled_task ​

Cancel permanently — the task will never fire again. destructive · user

ParameterTypeDescription
taskIdstring (required)UUID or SID