cron_update
Update a cron trigger's schedule, IANA timezone, handler, payload, display name, or enabled state. Sending a new schedule or timezone recomputes the next fire and re-checks the plan minimum (see cron_list policy); every other edit, including resuming a paused task, leaves an existing schedule alone.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"cron_id": "<cron_id>"
},
"name": "cron_update"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | New display name | |
| cron_id | Yes | The cron ID | |
| enabled | No | Enable or disable future fires | |
| handler | No | New project-relative /api path or full https:// URL the platform will POST to | |
| payload | No | New JSON object or JSON string passed to the handler | |
| schedule | No | New 5-field cron expression. Re-checked against the plan floor; omitted, the current schedule is untouched. | |
| timezone | No | New IANA timezone, e.g. America/Los_Angeles. Changing it recomputes next_run_at; omitted, the current timezone stays. |