Skip to main content
Glama
rishipradeep-think41

Google Workspace MCP Server

update_event

Modify existing calendar events by updating attendees, description, start/end times, location, or title using the Google Workspace MCP Server tool.

Instructions

Update an existing calendar event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attendeesNoNew list of attendee email addresses
descriptionNoNew event description
endNoNew end time in ISO format
eventIdYesEvent ID to update
locationNoNew event location
startNoNew start time in ISO format
summaryNoNew event title

Implementation Reference

  • Executes the update_event tool: patches the specified Google Calendar event with updated fields (summary, location, description, start, end, attendees) using Google Calendar API v3.
    private async handleUpdateEvent(args: any) {
      try {
        const { eventId, summary, location, description, start, end, attendees } =
          args;
    
        const event: any = {};
        if (summary) event.summary = summary;
        if (location) event.location = location;
        if (description) event.description = description;
        if (start) {
          event.start = {
            dateTime: start,
            timeZone: Intl.DateTimeFormat().resolvedOptions().timeZone,
          };
        }
        if (end) {
          event.end = {
            dateTime: end,
            timeZone: Intl.DateTimeFormat().resolvedOptions().timeZone,
          };
        }
        if (attendees) {
          event.attendees = attendees.map((email: string) => ({ email }));
        }
    
        const response = await this.calendar.events.patch({
          calendarId: "primary",
          eventId,
          requestBody: event,
        });
    
        return {
          content: [
            {
              type: "text",
              text: `Event updated successfully. Event ID: ${response.data.id}`,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: "text",
              text: `Error updating event: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema defining the parameters for the update_event tool: eventId (required), optional summary, location, description, start, end, attendees.
    inputSchema: {
      type: "object",
      properties: {
        eventId: {
          type: "string",
          description: "Event ID to update",
        },
        summary: {
          type: "string",
          description: "New event title",
        },
        location: {
          type: "string",
          description: "New event location",
        },
        description: {
          type: "string",
          description: "New event description",
        },
        start: {
          type: "string",
          description: "New start time in ISO format",
        },
        end: {
          type: "string",
          description: "New end time in ISO format",
        },
        attendees: {
          type: "array",
          items: { type: "string" },
          description: "New list of attendee email addresses",
        },
      },
      required: ["eventId"],
    },
  • src/index.ts:216-254 (registration)
    Registration of the update_event tool in the tools list returned by ListToolsRequestHandler, including name, description, and input schema.
    {
      name: "update_event",
      description: "Update an existing calendar event",
      inputSchema: {
        type: "object",
        properties: {
          eventId: {
            type: "string",
            description: "Event ID to update",
          },
          summary: {
            type: "string",
            description: "New event title",
          },
          location: {
            type: "string",
            description: "New event location",
          },
          description: {
            type: "string",
            description: "New event description",
          },
          start: {
            type: "string",
            description: "New start time in ISO format",
          },
          end: {
            type: "string",
            description: "New end time in ISO format",
          },
          attendees: {
            type: "array",
            items: { type: "string" },
            description: "New list of attendee email addresses",
          },
        },
        required: ["eventId"],
      },
    },
  • src/index.ts:286-289 (registration)
    Routing case in the CallToolRequestHandler switch statement that dispatches update_event calls to the handleUpdateEvent method.
    case "update_event":
      return await this.handleUpdateEvent(request.params.arguments);
    case "delete_event":
      return await this.handleDeleteEvent(request.params.arguments);
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's an update operation without disclosing behavioral traits. It doesn't mention permission requirements, whether changes are reversible, rate limits, or what happens to unspecified fields (partial vs. full updates). This is inadequate for a mutation tool with zero annotation coverage.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary elaboration.

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

Completeness2/5

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

For a mutation tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral nuances, leaving significant gaps despite the good schema coverage. More context is needed for safe and effective use.

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 parameters are well-documented in the schema. The description adds no additional meaning beyond implying an 'eventId' is needed (implied by 'existing'), which is already covered in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('Update') and resource ('an existing calendar event'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'modify_email' or specify what aspects of the event can be updated beyond the generic term.

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?

No guidance is provided on when to use this tool versus alternatives like 'create_event' or 'delete_event'. The description lacks context about prerequisites (e.g., needing an existing event ID) or exclusions, leaving the agent to infer usage from the name alone.

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/rishipradeep-think41/gsuite-mcp'

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