Skip to main content
Glama
taylorwilsdon

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

Manage Event

manage_event
Destructive

Create, update, delete, or RSVP to Google Calendar events. Handle attendees, reminders, recurrence, locations, and conference details.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform - "create", "update", "delete", or "rsvp".
summaryNoEvent title (required for create).
color_idNoEvent color ID (1-11, update only).
end_timeNoEnd time in RFC3339 format (required for create).
event_idNoEvent ID (required for update and delete).
locationNoEvent location.
responseNoRSVP response — "accepted", "declined", "tentative", or "needsAction" (rsvp action only).
timezoneNoTimezone (e.g., "America/New_York").
attendeesNoAttendee email addresses or objects.
remindersNoCustom reminder objects.
recurrenceNoRFC5545 recurrence rules for a recurring event, e.g. ["RRULE:FREQ=WEEKLY;COUNT=10"].
start_timeNoStart time in RFC3339 format (required for create).
visibilityNo"default", "public", "private", or "confidential".
attachmentsNoList of Google Drive file URLs or IDs to attach.
calendar_idNoCalendar ID (default: 'primary').primary
descriptionNoEvent description.
rsvp_commentNoOptional message to include with the RSVP response (rsvp action only).
send_updatesNoNotification behavior for create, update, delete, and rsvp — "all" (default), "externalOnly", or "none".
transparencyNo"opaque" (busy) or "transparent" (free).
conference_idNoOptional provider-side conference/meeting ID.
conference_uriNoJoin URL for the third-party conference (e.g. "https://zoom.us/j/123456789"). Required when conference_provider is set.
add_google_meetNoWhether to add/remove native Google Meet.
conference_dataNoRaw 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_modifyNoWhether attendees can modify.
user_google_emailYesThe user's Google email address. Required.
conference_passcodeNoOptional passcode for the third-party conference.
conference_providerNoHigher-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_remindersNoWhether to use default reminders.
guests_can_invite_othersNoWhether attendees can invite others.
guests_can_see_other_guestsNoWhether attendees can see other guests.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false. The description adds the RSVP capability, but no deeper behavioral context (e.g., notification side effects, that updates can be partial) is provided. It does not contradict the annotations.

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?

The description is only two short sentences with no redundant content. It is front-loaded with the core purpose and the operation list, earning both sentences.

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?

Despite having 30 parameters, the schema provides rich descriptions for each, and an output schema exists. The description orients the agent to the tool's broad purpose, though it could have added one line about the action-driven parameter usage. Overall, the structured data compensates for the minimal description.

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 schema already explains all parameters. The description only echoes the action enum values (create/update/delete/rsvp) already present in the schema, adding marginal semantic value beyond the structured data.

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?

The description clearly states the tool manages calendar events and lists the supported operations (creating, updating, deleting, and RSVP), which goes beyond a generic verb and distinguishes it from read-only siblings like get_events and manage_out_of_office.

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 description implies usage for calendar event mutations but does not explicitly state when to use it vs alternatives, nor any exclusions. The distinction from read-only tools like get_events is left to the agent to infer.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taylorwilsdon/google_workspace_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server