Skip to main content
Glama
redesignhealth

Google Workspace MCP Server

modify_event

Update existing Google Calendar events by changing details like title, time, location, attendees, reminders, or adding Meet conferencing. Adjust event visibility and availability as needed.

Instructions

Modifies an existing event.

Args: user_google_email (str): The user's Google email address. Required. event_id (str): The ID of the event to modify. calendar_id (str): Calendar ID (default: 'primary'). summary (Optional[str]): New event title. start_time (Optional[str]): New start time (RFC3339, e.g., "2023-10-27T10:00:00-07:00" or "2023-10-27" for all-day). end_time (Optional[str]): New end time (RFC3339, e.g., "2023-10-27T11:00:00-07:00" or "2023-10-28" for all-day). description (Optional[str]): New event description. location (Optional[str]): New event location. attendees (Optional[Union[List[str], List[Dict[str, Any]]]]): Attendees as email strings or objects with metadata. Supports: ["email@example.com"] or [{"email": "email@example.com", "responseStatus": "accepted", "organizer": true, "optional": true}]. When using objects, existing metadata (responseStatus, organizer, optional) is preserved. New attendees default to responseStatus="needsAction". timezone (Optional[str]): New timezone (e.g., "America/New_York"). add_google_meet (Optional[bool]): Whether to add or remove Google Meet video conference. If True, adds Google Meet; if False, removes it; if None, leaves unchanged. reminders (Optional[Union[str, List[Dict[str, Any]]]]): JSON string or list of reminder objects to replace existing reminders. Each should have 'method' ("popup" or "email") and 'minutes' (0-40320). Max 5 reminders. Example: '[{"method": "popup", "minutes": 15}]' or [{"method": "popup", "minutes": 15}] use_default_reminders (Optional[bool]): Whether to use calendar's default reminders. If specified, overrides current reminder settings. transparency (Optional[str]): Event transparency for busy/free status. "opaque" shows as Busy, "transparent" shows as Available/Free. If None, preserves existing transparency setting. visibility (Optional[str]): Event visibility. "default" uses calendar default, "public" is visible to all, "private" is visible only to attendees, "confidential" is same as private (legacy). If None, preserves existing visibility setting. color_id (Optional[str]): Event color ID (1-11). If None, preserves existing color.

Returns: str: Confirmation message of the successful event modification with event link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryNo
color_idNo
end_timeNo
event_idYes
locationNo
timezoneNo
attendeesNo
remindersNo
start_timeNo
visibilityNo
calendar_idNoprimary
descriptionNo
transparencyNo
add_google_meetNo
user_google_emailYes
use_default_remindersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full responsibility for behavior. It discloses important behavior: add_google_meet adds or removes a Google Meet conference, reminders 'replaces existing reminders' with a max of 5, and all optional fields preserve existing settings when None. It also explains attendee metadata preservation and default needsAction. Lacks details on auth or undo, but is solid overall.

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 structured as a docstring: one-line purpose, organized Args list, and Returns. It is long due to 16 parameters, but every sentence provides necessary information—formats, examples, defaults, and edge-case behavior—without fluff.

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?

The tool has 16 parameters and an output schema; the description covers all parameters, specifies required fields, includes examples, and states the return type. It omits error conditions and prerequisites (e.g., auth), but for a modification tool this is fairly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates with detailed, actionable semantics: RFC3339 examples, all-day date support, attendee object structures, reminder examples, and explicit meaning of None for each field. This goes far beyond the schema's bare types and defaults.

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 opens with 'Modifies an existing event,' which clearly states the verb (modify) and resource (existing event). This distinguishes it from sibling tools like create_event, delete_event, and get_events by its specific action.

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?

No explicit when-to-use or alternative guidance is provided. Usage is implied by the action: if you have an event_id and want to change fields, this is the tool. The description does not mention alternatives like create_event for new events or get_events for retrieval.

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/redesignhealth/google-mcp-unofficial'

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