Skip to main content
Glama
taylorwilsdon

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

modify_event

Edit existing calendar events by updating details such as title, time, location, attendees, and description. Designed for Google Workspace users to manage events efficiently.

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[List[str]]): New attendee email addresses.
    timezone (Optional[str]): New timezone (e.g., "America/New_York").

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attendeesNo
calendar_idNoprimary
descriptionNo
end_timeNo
event_idYes
locationNo
serviceYes
start_timeNo
summaryNo
timezoneNo
user_google_emailYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool modifies events and returns a confirmation message with a link, which adds some behavioral context. However, it doesn't cover critical aspects like authentication needs, error handling, rate limits, or what happens if parameters conflict with existing event data.

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?

The description is well-structured with clear sections for Args and Returns, making it easy to parse. It's appropriately sized, with each sentence adding necessary information. However, the parameter list is lengthy, which is unavoidable given the tool's complexity, but it remains efficient without wasted words.

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?

Given the complexity (11 parameters, no annotations, no output schema), the description is moderately complete. It covers parameters thoroughly and includes return information, but lacks behavioral details like error cases, permissions, or side effects. For a mutation tool with no structured support, it should provide more context on risks and outcomes.

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?

The schema description coverage is 0%, so the description must compensate. It provides detailed semantics for all 11 parameters, including data types, optionality, defaults, and examples (e.g., RFC3339 format for times). This adds significant value beyond the bare schema, fully documenting parameter meanings and usage.

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?

The description clearly states the tool's purpose with 'Modifies an existing event,' which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'create_event' or 'delete_event,' though the verb 'modifies' implies it's for updates rather than creation or deletion.

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?

The description provides no guidance on when to use this tool versus alternatives like 'create_event' or 'delete_event.' It lacks context about prerequisites, such as needing an existing event ID, and doesn't mention any exclusions or specific scenarios for usage.

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

Related 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