Update calendar event
well_update_calendar_eventChange an event on one of the user's own Google calendars: its title, time, guests, place, description or repeat rule.
Use this tool when the user asks to move, rename, reschedule or change a meeting. Find the event first with well_list_calendar_events or well_get_calendar_event. Skip the lookup only when the user gave its event_id and either the event is not repeating or the user gave the exact start of the occurrence.
REQUIRED: event_id, scope, notify_attendees. Send only the fields that change. scope is "occurrence" to change just one meeting of a repeating event, or "series" for all of them; for a single event either value changes that event. For one occurrence of a repeating event, also send occurrence_start, a timestamp with an offset (2026-10-12T10:00:00+02:00): the exact start the user gave, or else the occurrence_start value the list returned for it. Never guess it: if the user gave only a day, look the occurrence up with well_list_calendar_events first. For a repeating event, ask the user whether they mean this one occurrence or the whole series, and pass their answer as scope. Never assume it. Ask the user whether the guests should be emailed about the change, and pass their answer as notify_attendees (true or false). Never assume it. Times: start_at and end_at go together, as timestamps with an offset (2026-10-12T10:00:00+02:00) or as dates (2026-10-12) with is_all_day true. The times the user gives are read in the user's zone: send them with the user's offset from well_convert_time and leave timezone out, because the event keeps its own zone. Send timezone, an IANA name (such as Europe/Paris), only with change_timezone true, when the user asks to move the event to another zone. A repeating series keeps its own zone: naming another zone for a series without change_timezone is refused, so send the call again without timezone, unless the user asked to move the series. If a lookup shows the event has no timezone, do not guess one: ask the user, and send the user's zone only after they confirm it. attendees replaces the whole guest list. The repeat rule (recurrence) only changes on the series. Only the user's own calendars can be changed. If the user has not granted calendar access, the call fails with calendar_scope_not_granted and a link: give that link to the user as it is.
Returns { success: true, event_id, title, start_at, end_at } on success, or { success: false, error } on failure.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | Yes | ||
| title | No | ||
| end_at | No | ||
| event_id | Yes | The event to change, from well_list_calendar_events or well_get_calendar_event | |
| location | No | ||
| start_at | No | ||
| timezone | No | ||
| attendees | No | ||
| is_all_day | No | ||
| recurrence | No | ||
| visibility | No | ||
| description | No | ||
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which. | |
| change_timezone | No | true only when the user asks to move a repeating event to another time zone; without it the series keeps its own zone | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| idempotency_key | No | Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. | |
| notify_attendees | Yes | ||
| occurrence_start | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| title | No | ||
| end_at | No | ||
| success | Yes | ||
| event_id | No | ||
| start_at | No | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. |