Skip to main content
Glama

calendar_update_event

Update an existing event in the connected calendar (Google, Outlook or a CalDAV calendar). Can modify title, time, location, description, and attendees, add an online meeting link (Google Meet or Teams) to an event that has none, and move the event to another calendar of the same account. Only specified fields will be updated.

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": {
      "event_id": "<event_id>"
    },
    "name": "calendar_update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoNew end time in ISO 8601 format. Optional.
startNoNew start time in ISO 8601 format. Optional.
summaryNoNew event title/summary. Optional.
event_idYesID of the event to update. Required.
locationNoNew event location. Optional.
timezoneNoIANA timezone (e.g. 'Asia/Bishkek') that a new start/end WITHOUT an offset is in: the zone of the person the time was agreed with. OMIT only when that is the calendar's own zone. Same meaning as on calendar.create_event.
attendeesNoFull list of attendee emails the event should have; anyone not listed is removed, an empty list removes everyone. On Google calendars guests already on the event keep their RSVP. On Outlook calendars Microsoft Graph may reset their responses when the list is re-sent. To change only some guests use add_attendees / remove_attendees instead of resending the list.
account_idNoCalendar account to use when the workspace has several (Google, Outlook or CalDAV). OMIT to use the default one; every answer names the account and channel used.
calendar_idNoCalendar ID containing the event. OMIT to use the agent's configured default calendar (or primary).
descriptionNoNew event description. Optional.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
add_attendeesNoEmails to ADD to the event's current guests; the others stay invited (on Google with their RSVP; on Outlook Microsoft Graph may reset responses when it saves the list). Prefer this to `attendees` when inviting someone.
add_google_meetNoOld name of add_online_meeting (kept for existing agents). OMIT; use add_online_meeting.
move_to_calendarNoMove the event to another calendar of the same Google account, named by its id or its name, case-insensitive (e.g. a separate calendar kept for one project, so it can be shown or hidden on its own). The event keeps its id, Meet link and attendees, and the move itself notifies nobody (a field changed in the same call still notifies the attendees, as any update does). Calendar auto-join reads the primary calendar only, so the meeting bot does not join an event moved out of it. OMIT to leave the event where it is.
remove_attendeesNoEmails to REMOVE from the event's current guests; the others are untouched.
add_online_meetingNoIf true, gives the event a video meeting link of its own when it has none (Google Meet on a Google calendar, Microsoft Teams on an Outlook calendar); an event that already has one keeps it. OMIT to leave the event's link as it is.
send_notificationsNoWhether to email the attendees about the change. true (default) notifies them; false saves the change silently. On Outlook calendars a silent save is refused when the event has guests. Moving an event to another calendar never notifies the guests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / account_id / description
      Previous value: -"Calendar account to use when the workspace has several (Google or Outlook). OMIT to use the default one; every answer names the account and channel used."New value: +"Calendar account to use when the workspace has several (Google, Outlook or CalDAV). OMIT to use the default one; every answer names the account and channel used."
  2. Changed3 schema fields changed
    • addedInput schema / properties / add_attendees
      Added value: +{
      +  "description": "Emails to ADD to the event's current guests; the others stay invited (on Google with their RSVP; on Outlook Microsoft Graph may reset responses when it saves the list). Prefer this to `attendees` when inviting someone.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / attendees / description
      Previous value: -"New list of attendee emails. Replaces existing attendees."New value: +"Full list of attendee emails the event should have; anyone not listed is removed, an empty list removes everyone. On Google calendars guests already on the event keep their RSVP. On Outlook calendars Microsoft Graph may reset their responses when the list is re-sent. To change only some guests use add_attendees / remove_attendees instead of resending the list."
    • addedInput schema / properties / remove_attendees
      Added value: +{
      +  "description": "Emails to REMOVE from the event's current guests; the others are untouched.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / timezone
      Added value: +{
      +  "description": "IANA timezone (e.g. 'Asia/Bishkek') that a new start/end WITHOUT an offset is in: the zone of the person the time was agreed with. OMIT only when that is the calendar's own zone. Same meaning as on calendar.create_event.",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / send_notifications
      Added value: +{
      +  "default": true,
      +  "description": "Whether to email the attendees about the change. true (default) notifies them; false saves the change silently. On Outlook calendars a silent save is refused when the event has guests. Moving an event to another calendar never notifies the guests.",
      +  "type": "boolean"
      +}
  5. Changed3 schema fields changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Calendar account to use when the workspace has several (Google or Outlook). OMIT to use the default one; every answer names the account and channel used.",
      +  "type": "integer"
      +}
    • changedInput schema / properties / add_google_meet / description
      Previous value: -"If true, gives the event a Google Meet link of its own when it has none; an event that already has one keeps it. OMIT to leave the event's link as it is."New value: +"Old name of add_online_meeting (kept for existing agents). OMIT; use add_online_meeting."
    • addedInput schema / properties / add_online_meeting
      Added value: +{
      +  "description": "If true, gives the event a video meeting link of its own when it has none (Google Meet on a Google calendar, Microsoft Teams on an Outlook calendar); an event that already has one keeps it. OMIT to leave the event's link as it is.",
      +  "type": "boolean"
      +}
  6. Changed1 schema field changed
    • addedInput schema / properties / move_to_calendar
      Added value: +{
      +  "description": "Move the event to another calendar of the same Google account, named by its id or its name, case-insensitive (e.g. a separate calendar kept for one project, so it can be shown or hidden on its own). The event keeps its id, Meet link and attendees, and the move itself notifies nobody (a field changed in the same call still notifies the attendees, as any update does). Calendar auto-join reads the primary calendar only, so the meeting bot does not join an event moved out of it. OMIT to leave the event where it is.",
      +  "type": "string"
      +}
  7. Changed1 schema field changed
    • addedInput schema / properties / add_google_meet
      Added value: +{
      +  "description": "If true, gives the event a Google Meet link of its own when it has none; an event that already has one keeps it. OMIT to leave the event's link as it is.",
      +  "type": "boolean"
      +}
  8. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  9. Added
  10. Removed
  11. Changed2 schema fields changed
    • removedInput schema / properties / calendar_id / default
      Removed value: -"primary"
    • changedInput schema / properties / calendar_id / description
      Previous value: -"Calendar ID containing the event. Defaults to primary."New value: +"Calendar ID containing the event. OMIT to use the agent's configured default calendar (or primary)."
  12. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the mutation and open-world profile; the description adds the important PATCH-style contract ("Only specified fields will be updated") and the behavior that an event with an existing meeting link keeps it (via schema) and that moves preserve id, link and attendees. One tension goes unaddressed in the description: annotations say destructiveHint=false, yet replacing `attendees` silently removes anyone not listed — that removal risk lives only in the schema, not in the prose.

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?

Two sentences, front-loaded with the verb+resource and followed by the capability list plus the partial-update guarantee. Dense but every clause maps to a real capability; no filler.

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 17-parameter, multi-provider mutation with no output schema, the description covers the capability envelope and the partial-update contract, while the fully documented schema handles per-field semantics and notifications. An agent could act correctly from this definition, though notification side effects (send_notifications, Outlook silent-save refusal) are left entirely to the schema.

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

Parameters3/5

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

Schema description coverage is 100%, so the parameters are already fully self-documenting, and the description mostly mirrors them (title, time, location, description, attendees, meeting link, move). It adds little new meaning beyond what the schema states for individual fields. Baseline 3 applies when the schema carries the weight.

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?

"Update an existing event in the connected calendar (Google, Outlook or a CalDAV calendar)" gives a specific verb and resource, then enumerates the modifiable surfaces (title, time, location, description, attendees, meeting link, calendar move). An agent can distinguish this from calendar_create_event and calendar_delete_event without opening the schema.

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

Usage Guidelines4/5

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

The description establishes that this is for an event that already exists and that non-listed fields are untouched, and the schema explicitly prefers add_attendees/remove_attendees over resending `attendees`. It stops short of naming sibling tools (e.g. calendar_create_event) or stating when a delete-and-recreate would be preferable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.