Skip to main content
Glama
Sign In
google-services-mcp

google-services-mcp

by nabheet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update calendar event

google_calendar_update_event

Partially update an existing Google Calendar event—change its title, time, location, attendees, recurrence, or reminders without replacing the full event object.

Instructions

Update fields of an existing event (partial update).

Input Schema

NameRequiredDescriptionDefault
endNoNew end RFC3339 datetime (or YYYY-MM-DD for all-day). Given alone, the start keeps the current duration.
startNoNew start RFC3339 datetime (or YYYY-MM-DD for all-day). Given alone, the end keeps the current duration.
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. Changed2 schema fields changedv0.1.95
    • changedInput schema / properties / end / description
      Previous value: -"New end RFC3339 datetime."New value: +"New end RFC3339 datetime (or YYYY-MM-DD for all-day). Given alone, the start keeps the current duration."
    • changedInput schema / properties / start / description
      Previous value: -"New start RFC3339 datetime."New value: +"New start RFC3339 datetime (or YYYY-MM-DD for all-day). Given alone, the end keeps the current duration."
  2. 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"
+}
  3. 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,}$"
  4. 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 burden and delivers almost nothing: it doesn't say that attendee updates replace the whole list, that changes may trigger notification emails (sendUpdates), whether changes apply to recurring instances, or whether the operation is reversible. The only behavioral disclosure is the '(partial update)' note.

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 no filler or repetition. It is efficient, though its brevity is partly under-specification rather than true density.

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 17-parameter mutation tool with zero annotations and no output schema, one sentence is not enough: risks of overwriting attendees/recurrence, notification side effects, and account/calendar scoping all go unaddressed. Only the schema carries the 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%, so the schema already documents nearly all 17 parameters, including the subtle start/end duration behavior and enum meanings. The description adds no parameter meaning of its own, 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 and resource ('Update fields of an existing event') and clarifies the partial-update semantics, which is a meaningful distinction. It doesn't differentiate from nearby siblings like google_calendar_update or google_calendar_create_event, so it stops short of a 5.

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?

No when-to-use guidance, no prerequisites (eventId required, calendarId defaulting to primary), and no mention of when to prefer this over google_calendar_update or how it relates to google_calendar_get_event. '(partial update)' is the only usage hint and it is inferred rather than stated.

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