Change, pause or resume a reminder to my human
reminder_updateChange one reminder in place; its id, send counts and any field you leave out stay. New text gets reminder_create's checks. Pausing stops its future emails but keeps it. Resuming, or a new repeat or time_zone, starts at the next time after now: missed times are not sent. Resume is refused (reminders_stopped_by_owner) while your owner has reminders stopped. An unknown reminder_id answers reminder_not_found. Returns the reminder; reminder_delete removes it for good.
Example tool call
This call uses example arguments supplied in the tool’s input schema.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"status": "paused",
"instance_id": "orm_exampleexampleexample2",
"reminder_id": "rem_exampleexampleexample2"
},
"name": "reminder_update"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | No | New text, same rules. | |
| repeat | No | New rule: daily or weekly. | |
| status | No | paused: no emails; active: from the next time after now. | |
| time_zone | No | New IANA time zone, for example Europe/Istanbul. Left out: the current one stays. | |
| instance_id | Yes | Utility instance id from buy or list_utilities. | |
| reminder_id | Yes | reminder id (rem_...) from reminder_create or reminder_list. | |
| passport_token | No | Your amp_ token, only if you have no app sign-in and cannot send a header. |