Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Manage Event

manage_event

Destructive

Create, update, delete, and RSVP to Google Calendar events, including attendees, recurring meetings, and video conferences.

Instructions

Manages calendar events. Supports creating, updating, deleting, and RSVP.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	Yes	Action to perform - "create", "update", "delete", or "rsvp".
`summary`	No	Event title (required for create).
`color_id`	No	Event color ID (1-11, update only).
`end_time`	No	End time in RFC3339 format (required for create).
`event_id`	No	Event ID (required for update and delete).
`location`	No	Event location.
`response`	No	RSVP response — "accepted", "declined", "tentative", or "needsAction" (rsvp action only).
`timezone`	No	IANA timezone applied to both boundaries (e.g., "America/New_York"). Overridden per boundary by start_timezone/end_timezone.
`attendees`	No	Attendee email addresses or objects.
`reminders`	No	Custom reminder objects.
`recurrence`	No	RFC5545 recurrence rules for a recurring event, e.g. ["RRULE:FREQ=WEEKLY;COUNT=10"].
`start_time`	No	Start time in RFC3339 format (required for create).
`visibility`	No	"default", "public", "private", or "confidential".
`attachments`	No	List of Google Drive file URLs or IDs to attach. On action="update" this replaces the event's existing attachments rather than appending to them, matching the Calendar API's patch semantics.
`calendar_id`	No	Calendar ID (default: 'primary').	primary
`description`	No	Event description.
`end_timezone`	No	IANA timezone for the end boundary only, overriding timezone. See start_timezone.
`rsvp_comment`	No	Optional message to include with the RSVP response (rsvp action only).
`send_updates`	No	Notification behavior for create, update, delete, and rsvp — "all" (default), "externalOnly", or "none".
`transparency`	No	"opaque" (busy) or "transparent" (free).
`conference_id`	No	Optional provider-side conference/meeting ID.
`conference_uri`	No	Join URL for the third-party conference (e.g. "https://zoom.us/j/123456789"). Required when conference_provider is set.
`start_timezone`	No	IANA timezone for the start boundary only, overriding timezone. Use for events whose two ends sit in different zones - a flight departing 13:45 "Asia/Jerusalem" and landing 17:50 "Europe/Amsterdam" is one event authored in two zones. Passing a single timezone for such an event silently rewrites one end's wall-clock.
`add_google_meet`	No	Whether to add/remove native Google Meet.
`conference_data`	No	Raw Google Calendar `conferenceData` payload to attach a third-party conference (Zoom/Webex/Teams add-on). Use this for full control; mutually exclusive with the conference_provider helper params and with add_google_meet. (create/update only)
`guests_can_modify`	No	Whether attendees can modify.
`user_google_email`	Yes	The user's Google email address. Required.
`conference_passcode`	No	Optional passcode for the third-party conference.
`conference_provider`	No	Higher-level helper: third-party provider name (e.g. "zoom", "webex", "teams"). Requires conference_uri. The MCP builds the addOn `conferenceData` block internally. (create/update only)
`use_default_reminders`	No	Whether to use default reminders.
`guests_can_invite_others`	No	Whether attendees can invite others.
`guests_can_see_other_guests`	No	Whether attendees can see other guests.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.26.0Sep 6, 2026

changedInput schema / properties / attachments / description

Previous value: -"List of Google Drive file URLs or IDs to attach."New value: +"List of Google Drive file URLs or IDs to attach.\nOn action=\"update\" this replaces the event's existing attachments rather than\nappending to them, matching the Calendar API's patch semantics."

Changed3 schema fields changedv1.25.2Aug 30, 2026

addedInput schema / properties / end_timezone

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "IANA timezone for the end boundary only,\noverriding timezone. See start_timezone."
+}

addedInput schema / properties / start_timezone

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "IANA timezone for the start boundary only,\noverriding timezone. Use for events whose two ends sit in different zones -\na flight departing 13:45 \"Asia/Jerusalem\" and landing 17:50\n\"Europe/Amsterdam\" is one event authored in two zones. Passing a single\ntimezone for such an event silently rewrites one end's wall-clock."
+}

changedInput schema / properties / timezone / description

Previous value: -"Timezone (e.g., \"America/New_York\")."New value: +"IANA timezone applied to both boundaries (e.g.,\n\"America/New_York\"). Overridden per boundary by start_timezone/end_timezone."

Addedv1.0.1Jul 31, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already disclose the safety profile (destructiveHint=true, readOnlyHint=false), and the description is consistent with them — "deleting" matches the destructive hint. The description adds no further behavioral context (notification behavior, deletion permanence, attachment patch-replace semantics), and the one meaningful schema note on that is tucked into a parameter description. No contradiction with annotations, so not a 1, but the description contributes minimal signal beyond the structured hints.

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 short sentences with the resource front-loaded and zero filler; the action enumeration in the second sentence earns its place. It is efficient but extremely terse for a 32-parameter, four-action tool, so there is room for one framing clause (e.g., that parameter requirements are action-dependent) before it is optimally sized.

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

Completeness3/5

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

The output schema, 100%-covered parameter schema, and annotations already carry most of the burden, so the thin description is not crippling. What is missing is mode-specific guidance (which parameters each action needs, though the schema covers this) and routing among siblings such as get_events for reading or create_calendar for calendar-level operations. For a tool this complex, a small amount of cross-tool routing would materially improve completeness.

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%, with all 32 parameters individually documented including action-scoped requirements ("required for create", "update only", "rsvp action only") and subtleties like dual-timezone overrides and attachment replacement semantics. The description's only parameter-adjacent content is the action enumeration, which maps directly onto the action parameter. Baseline 3 applies because the schema carries the full burden.

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?

Names the resource ("calendar events") and enumerates all four operations (create, update, delete, RSVP), making its scope immediately legible and distinguishing its intent from read-only event tools like get_events. It earns a 4 rather than 5 because "manages" is a generic umbrella verb and no sibling is named for explicit contrast.

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 action list implies usage context — invoke this when an event must be created, updated, deleted, or RSVP'd — but the description never states when not to use it (e.g., reading events via get_events, or calendar-level operations via create_calendar). No exclusions or alternatives are given; per-action parameter requirements are left entirely to the schema.

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

Deploy Server