Skip to main content
Glama
dipseth

google-workspace-unlimited

Modify Calendar Event

modify_event

Update an existing Google Calendar event by changing its details such as title, time, location, description, attendees, or recurrence. Only specified fields are modified.

Instructions

Modifies an existing event in Google Calendar. TIMEZONE: Always pass the timezone parameter or include UTC offsets in start_time/end_time to avoid time offset issues. Uses PATCH semantics — only specified fields are changed, unspecified fields (including recurrence rules) are preserved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryNoNew event title/summary
durationNoEvent duration as alternative to end_time (requires start_time). Format: a number + unit — '30s', '5m', '2h', '1.5d', '1w'. Ignored if end_time is also provided.
end_timeNoNew end time. Required unless 'duration' is provided alongside start_time. IMPORTANT: Always specify timezone to avoid time offset issues. Preferred: datetime with offset (e.g., '2023-10-27T11:00:00-07:00') or UTC ('2023-10-27T11:00:00Z'). Naive datetimes are localized using the timezone param or server default. Date only for all-day events (e.g., '2023-10-28').
event_idYesThe ID of the event to modify
locationNoNew event location (e.g., '123 Main St' or 'https://meet.google.com/abc-defg-hij')
timezoneNoSTRONGLY RECOMMENDED when using naive datetimes. IANA timezone name (e.g., 'America/New_York', 'America/Chicago'). Naive datetimes in start_time/end_time will be interpreted in this timezone. Without this, the server's DEFAULT_TIMEZONE setting is used.
attendeesNoNew list of attendee email addresses
recurrenceNoList of RRULE, EXRULE, RDATE, or EXDATE strings for recurring events (e.g., ['RRULE:FREQ=WEEKLY;BYDAY=MO,WE,FR']). See RFC 5545.
start_timeNoNew start time. IMPORTANT: Always specify timezone to avoid time offset issues. Preferred: datetime with offset (e.g., '2023-10-27T10:00:00-07:00') or UTC ('2023-10-27T10:00:00Z'). Naive datetimes are localized using the timezone param or server default. Date only for all-day events (e.g., '2023-10-27').
calendar_idNoCalendar ID where the event is locatedprimary
descriptionNoNew event description/details
user_google_emailNoThe user's Google email address for Calendar access. If None, uses the current authenticated user from FastMCP context (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
eventIdYes
messageYes
successYes
summaryYes
htmlLinkYes
userEmailYes
calendarIdYes
fieldsModifiedYes
Behavior4/5

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

Adds valuable context beyond annotations: explains PATCH semantics (only specified fields changed, unspecified preserved) and stress on timezone handling. No contradiction with annotations (readOnlyHint false, destructiveHint false).

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 sentences, each essential. First states purpose, second gives critical timezone advice, third explains PATCH semantics. No redundant information.

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

Completeness5/5

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

For a tool with 12 parameters and an output schema, the description covers key behavioral aspects (timezone, PATCH) and leaves parameter details to the schema, which is appropriate. No gaps identified.

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 baseline is 3. The description adds overall context (timezone, PATCH) but does not significantly enhance per-parameter meaning beyond what the schema already provides.

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?

Clearly states 'Modifies an existing event in Google Calendar', which is a specific verb+resource combination. Distinguishes from sibling tools like create_event and delete_event.

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

Usage Guidelines4/5

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

Provides explicit guidance on timezone handling and PATCH semantics, which helps in correct usage. However, does not explicitly state when not to use or compare with alternatives beyond the implicit distinction from siblings.

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/dipseth/google_workspace_fastmcp2'

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