Update calendar event
update_calendar_eventEdit or reschedule an existing calendar event by passing its uid and only the fields to change; omitted fields keep stored values. Update time, title, location, attendees, or reminders.
Instructions
Update, edit or reschedule an existing calendar event or meeting: move it to a new time, change the time or title, set the location, or add and remove attendees. Pass the event uid (from list_calendar_events or create_calendar_event) plus only the fields to change — every field you omit keeps its stored value, so rescheduling needs nothing but uid and start. All-day events stay all-day; pass start/end as dates or date-times to switch. Set or clear a reminder with reminderMinutesBefore. Attendees are re-notified by iMIP unless you pass notify: "none". To change one occurrence of a repeating series instead of the whole series, pass recurrenceId. To rename or recolor a calendar itself, use update_calendar. To put an event on a different calendar, use move_calendar_events.
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": {
"uid": "<uid>"
},
"name": "update_calendar_event"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | New end, ISO 8601, or an exclusive date for an all-day event. Omit to keep the event’s length when moving `start`, its stored end otherwise. | |
| uid | Yes | ||
| start | No | New start, ISO 8601, or a date (2026-10-03) for an all-day event. Omit to keep the stored start. | |
| title | No | New title. Omit to keep the stored one. | |
| notify | No | `all` (default) re-notifies the attendees by iMIP; `none` edits silently. | |
| location | No | New location; `""` clears it. Omit to keep the stored one. | |
| timeZone | No | IANA zone for the start/end you pass, e.g. Europe/Berlin: their clock digits are read as wall-clock time here, overriding any offset. Defaults to the event’s own stored zone. Times you omit keep theirs. | |
| attendees | No | The complete attendee list after the edit; `[]` uninvites everyone. Omit to keep the stored attendees, or use `addedAttendees`/`removedAttendees` instead. | |
| recurrence | No | New repeat rule for the whole series; "none" makes it a one-off. Omit to keep the stored rule. Either a raw RFC 5545 RRULE ("FREQ=WEEKLY;BYDAY=TH", "FREQ=DAILY;COUNT=10") or {frequency, interval?, byDay?, until?|count?}. Use at most one of until/count; The object’s `until` is ISO (2026-12-31 or 2026-12-31T00:00:00Z); a raw UNTIL is compact (20261231 or 20261231T000000Z). Either is converted to match the event (a date on an all-day series). A raw rule is only lightly validated, so a malformed one fails later at the server. | |
| calendarUrl | No | ||
| description | No | New description; `""` clears it. Omit to keep the stored one. | |
| recurrenceId | No | To change one occurrence of a repeating series alone, its original start as an ISO 8601 instant (e.g. 2026-06-16T10:00:00Z), or its date for an all-day series (2026-06-16). Not combinable with `recurrence`, `addedAttendees` or `removedAttendees`. | |
| addedAttendees | No | Email addresses to invite on top of the stored attendees. Cannot be combined with `attendees`. | |
| removedAttendees | No | Email addresses to uninvite (case-insensitive). Cannot be combined with `attendees`. | |
| reminderMinutesBefore | No | Minutes before the start to remind the user (all-day events start at 00:00, so 900 = 09:00 the day before); replaces any stored reminders. "none" removes them. Omit to keep the stored ones. |