Skip to main content
Glama
nabheet

google-services-mcp

by nabheet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update calendar event

google_calendar_update_event

Update an existing Google Calendar event with a partial update, so you can change only needed fields like time, title, location, attendees, or reminders.

Instructions

Update fields of an existing event (partial update).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoNew end RFC3339 datetime.
startNoNew start RFC3339 datetime.
accountNoAccount nickname to use.
colorIdNoEvent color ID (1-11).
eventIdYesEvent ID.
summaryNo
locationNo
timeZoneNoIANA time zone, e.g. America/Denver. Required when updating to recurring timed events.
attendeesNoFull attendee list.
calendarIdNoCalendar ID (default primary).
recurrenceNoRRULE strings, e.g. ["RRULE:FREQ=WEEKLY;BYDAY=TH"].
descriptionNo
sendUpdatesNoControl attendee notification emails.
transparencyNoShow as busy (opaque) or free (transparent).
reminderMethodNoReminder delivery method.
reminderMinutesNoMinutes before event.
remindersUseDefaultNoUse calendar default reminders instead of overrides.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.60
    • addedInput schema / properties / colorId
      Added value: +{
+  "description": "Event color ID (1-11).",
+  "type": "string"
+}
    • addedInput schema / properties / recurrence
      Added value: +{
+  "description": "RRULE strings, e.g. [\"RRULE:FREQ=WEEKLY;BYDAY=TH\"].",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / reminderMethod
      Added value: +{
+  "description": "Reminder delivery method.",
+  "enum": [
+    "email",
+    "popup"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / reminderMinutes
      Added value: +{
+  "description": "Minutes before event.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / remindersUseDefault
      Added value: +{
+  "description": "Use calendar default reminders instead of overrides.",
+  "type": "boolean"
+}
    • addedInput schema / properties / sendUpdates
      Added value: +{
+  "description": "Control attendee notification emails.",
+  "enum": [
+    "all",
+    "externalOnly",
+    "none"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / timeZone
      Added value: +{
+  "description": "IANA time zone, e.g. America/Denver. Required when updating to recurring timed events.",
+  "type": "string"
+}
    • addedInput schema / properties / transparency
      Added value: +{
+  "description": "Show as busy (opaque) or free (transparent).",
+  "enum": [
+    "opaque",
+    "transparent"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.1.30
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / attendees / items / pattern
      Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  3. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and "partial update" is the only real disclosure — it usefully signals that unspecified fields are preserved. However, it says nothing about side effects (attendee notification emails triggered by sendUpdates), permission/auth requirements, whether changes are reversible, or how recurrence edits behave, all of which matter for a 17-parameter mutation.

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?

A single front-loaded sentence with zero filler, and the partial-update qualifier is placed where it is read first. It is arguably under-sized for a 17-parameter tool, which keeps it just short of a 5.

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

Completeness2/5

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

For a large mutation tool with no annotations, no output schema, and only one required parameter, a one-line description leaves the agent without the behavioral context it needs (notification side effects, auth, recurrence caveats). It is far too thin relative to the tool's complexity, even though the schema covers most parameter detail.

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 82%, well above the threshold where the schema does the heavy lifting, and the description adds no parameter-level detail whatsoever. Baseline 3 applies: the schema documents start/end/timeZone/recurrence/attendees semantics itself.

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 and resource ("Update fields of an existing event") and clarifies scope with "(partial update)." It distinguishes update from create/delete siblings, though it does nothing to differentiate itself from the similarly named google_calendar_update sibling.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus google_calendar_update, google_calendar_create_event, or google_calendar_respond, nor any statement of prerequisites such as needing an existing eventId or write access. The parenthetical "partial update" implies behavior but never states when a partial update is the right choice.

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

Deploy Server

Other Tools