Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

calendar_events_update

Destructive

Update an existing calendar event by changing only supplied fields; note that attendee lists are replaced, so omitted attendees are uninvited.

Instructions

Update an existing calendar event with patch semantics (only supplied fields change). attendees replaces the whole list and anyone omitted is uninvited. Because it can do that, the whole tool is marked destructive, including calls without attendees.

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": {
      "calendarId": "<calendarId>",
      "eventId": "<eventId>"
    },
    "name": "calendar_events_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd time JSON
startNoStart time JSON
eventIdYesEvent ID to update
summaryNoEvent title
attendeesNoREPLACES the full attendee list — Google's patch overwrites array fields, so include everyone who should remain; anyone omitted is uninvited. JSON array as string, e.g. '[{"email":"a@x.com"},{"email":"b@x.com","optional":true}]'
calendarIdYesCalendar ID
descriptionNoEvent description
sendUpdatesNoSends update email to attendees when set: "all", "externalOnly", or "none" (default: none — no email). With "all" or "externalOnly", attendees removed by this update receive a cancellation email. Omitted attendees are uninvited whatever this is set to; it only decides whether they are emailed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / sendUpdates / description
      Previous value: -"Sends update email to attendees when set: \"all\", \"externalOnly\", or \"none\" (default: none — no email). With \"all\" or \"externalOnly\", attendees removed by this update receive a cancellation email"New value: +"Sends update email to attendees when set: \"all\", \"externalOnly\", or \"none\" (default: none — no email). With \"all\" or \"externalOnly\", attendees removed by this update receive a cancellation email. Omitted attendees are uninvited whatever this is set to; it only decides whether they are emailed"
  2. Changed2 schema fields changedv0.4.1
    • addedInput schema / properties / attendees
      Added value: +{
      +  "description": "REPLACES the full attendee list — Google's patch overwrites array fields, so include everyone who should remain; anyone omitted is uninvited. JSON array as string, e.g. '[{\"email\":\"a@x.com\"},{\"email\":\"b@x.com\",\"optional\":true}]'",
      +  "type": "string"
      +}
    • addedInput schema / properties / sendUpdates
      Added value: +{
      +  "description": "Sends update email to attendees when set: \"all\", \"externalOnly\", or \"none\" (default: none — no email). With \"all\" or \"externalOnly\", attendees removed by this update receive a cancellation email",
      +  "enum": [
      +    "all",
      +    "externalOnly",
      +    "none"
      +  ],
      +  "type": "string"
      +}
  3. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds genuinely non-obvious context: it explains WHY the tool is destructive (attendee list replacement silently uninvites omitted people) and warns that even calls without attendees carry the destructive marking. It does not address permissions/scopes or reversibility, so not a 5.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the operation and its patch semantics, followed by the one hazard that matters most. No filler or redundant framing.

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 mutation tool with full annotation coverage, 100% schema descriptions, and no output schema, the description covers the essential behavioral risk an agent needs before calling. Minor gaps remain around auth requirements and confirmability, but nothing critical is missing.

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 coverage is 100% and the schema itself already documents attendees replacement semantics and sendUpdates email behavior in detail. The description restates the attendees hazard rather than adding new parameter meaning, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb (update) and resource (existing calendar event) plus the key semantic — patch-style partial update. It implicitly distinguishes itself from calendar_events_insert by saying 'existing,' but never names or contrasts any sibling explicitly.

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

Usage Guidelines3/5

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

The patch-semantics note tells an agent that only supplied fields change, which implies when to use this over a full replace. However, there is no explicit guidance contrasting it with calendar_events_insert, calendar_events_delete, or any sibling, leaving the choice to inference.

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