Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Update calendar event

update_calendar_event
Destructive

Edit 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

NameRequiredDescriptionDefault
endNoNew 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.
uidYes
startNoNew start, ISO 8601, or a date (2026-10-03) for an all-day event. Omit to keep the stored start.
titleNoNew title. Omit to keep the stored one.
notifyNo`all` (default) re-notifies the attendees by iMIP; `none` edits silently.
locationNoNew location; `""` clears it. Omit to keep the stored one.
timeZoneNoIANA 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.
attendeesNoThe complete attendee list after the edit; `[]` uninvites everyone. Omit to keep the stored attendees, or use `addedAttendees`/`removedAttendees` instead.
recurrenceNoNew 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.
calendarUrlNo
descriptionNoNew description; `""` clears it. Omit to keep the stored one.
recurrenceIdNoTo 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`.
addedAttendeesNoEmail addresses to invite on top of the stored attendees. Cannot be combined with `attendees`.
removedAttendeesNoEmail addresses to uninvite (case-insensitive). Cannot be combined with `attendees`.
reminderMinutesBeforeNoMinutes 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this is a destructive, non-idempotent, open-world write, so the safety bar is partly covered. The description still adds real behavioral context beyond them: omitted fields retain stored values (partial-update semantics), attendees are re-notified by iMIP unless `notify: "none"`, and all-day events stay all-day unless dates/date-times are supplied. It does not mention any permission requirements, error behavior, or what happens to attachments/invitees on failure, so it stops short of full disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the core partial-update rule are front-loaded, and the later sentences are each doing distinct work (reminders, notifications, occurrence targeting, sibling routing). It is dense but not padded; a slight trim of the enumerated field list in the opening sentence would tighten it further.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter mutation tool with no output schema, the definition covers the critical decision points: partial-update semantics, notification behavior, all-day handling, occurrence vs. series scope, and sibling alternatives. The main residual gap is that recurrence rules and timezone handling are left almost entirely to schema text, so an agent constructing a complex recurring edit must fall back on field descriptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 87%, so the baseline is 3, and the description earns extra credit by explaining the partial-update contract (omit = keep), the date-vs-date-time switch for all-day events, reminder clearing via `reminderMinutesBefore`, and the occurrence-scoping role of `recurrenceId`. However, several parameters — `recurrence`, `calendarUrl`, `timeZone`, `description` — are not discussed at all, leaving their cross-field interactions to the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Update, edit or reschedule an existing calendar event or meeting') and enumerates the concrete operations: retime, retitle, set location, add/remove attendees. It also names the sibling tools it is not (update_calendar for calendar-level changes, move_calendar_events for cross-calendar moves), so an agent can discriminate without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing rules and preconditions: pass `uid` from list_calendar_events or create_calendar_event, use `recurrenceId` for a single occurrence rather than the series, use update_calendar to rename a calendar, use move_calendar_events to relocate an event. The 'when not to use' alternatives are stated outright, which is rare and valuable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.