Skip to main content
Glama
peadams21

Google Calendar MCP Server

by peadams21

update_event

Modify existing Google Calendar events by updating details like title, time, location, or attendees to keep schedules accurate and current.

Instructions

Update an existing event in Google Calendar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarIdNoCalendar ID (default: 'primary')primary
eventIdYesEvent ID to update
summaryNoEvent title/summary
descriptionNoEvent description
startNo
endNo
locationNoEvent location
attendeesNoList of attendees

Implementation Reference

  • Handler function that updates an existing Google Calendar event using the Google Calendar API's events.patch method. Constructs update object from provided args and returns success/error response.
    async function handleUpdateEvent(args: z.infer<typeof UpdateEventArgsSchema>) {
      try {
        const updates: any = {};
        if (args.summary !== undefined) updates.summary = args.summary;
        if (args.description !== undefined) updates.description = args.description;
        if (args.start !== undefined) updates.start = args.start;
        if (args.end !== undefined) updates.end = args.end;
        if (args.location !== undefined) updates.location = args.location;
        if (args.attendees !== undefined) updates.attendees = args.attendees;
    
        const response = await calendar.events.patch({
          calendarId: args.calendarId,
          eventId: args.eventId,
          requestBody: updates,
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: true,
                event: response.data,
                message: `Event "${args.eventId}" updated successfully`,
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: false,
                error: error instanceof Error ? error.message : "Unknown error",
              }, null, 2),
            },
          ],
          isError: true,
        };
      }
  • Zod schema defining the input parameters for the update_event tool, used for validation in the request handler.
    const UpdateEventArgsSchema = z.object({
      calendarId: z.string().optional().default("primary"),
      eventId: z.string(),
      summary: z.string().optional(),
      description: z.string().optional(),
      start: z.object({
        dateTime: z.string(),
        timeZone: z.string().optional(),
      }).optional(),
      end: z.object({
        dateTime: z.string(),
        timeZone: z.string().optional(),
      }).optional(),
      location: z.string().optional(),
      attendees: z.array(z.object({
        email: z.string(),
        displayName: z.string().optional(),
      })).optional(),
    });
  • src/index.ts:223-291 (registration)
    MCP tool registration object defining the name, description, and JSON inputSchema for the update_event tool, provided in response to ListToolsRequest.
    {
      name: "update_event",
      description: "Update an existing event in Google Calendar",
      inputSchema: {
        type: "object",
        properties: {
          calendarId: {
            type: "string",
            description: "Calendar ID (default: 'primary')",
            default: "primary",
          },
          eventId: {
            type: "string",
            description: "Event ID to update",
          },
          summary: {
            type: "string",
            description: "Event title/summary",
          },
          description: {
            type: "string",
            description: "Event description",
          },
          start: {
            type: "object",
            properties: {
              dateTime: {
                type: "string",
                description: "Start date and time (RFC3339 timestamp)",
              },
              timeZone: {
                type: "string",
                description: "Time zone (e.g., 'America/New_York')",
              },
            },
          },
          end: {
            type: "object",
            properties: {
              dateTime: {
                type: "string",
                description: "End date and time (RFC3339 timestamp)",
              },
              timeZone: {
                type: "string",
                description: "Time zone (e.g., 'America/New_York')",
              },
            },
          },
          location: {
            type: "string",
            description: "Event location",
          },
          attendees: {
            type: "array",
            items: {
              type: "object",
              properties: {
                email: { type: "string" },
                displayName: { type: "string" },
              },
              required: ["email"],
            },
            description: "List of attendees",
          },
        },
        required: ["eventId"],
      },
    },
  • src/index.ts:555-558 (registration)
    Dispatch logic in CallToolRequest handler that validates arguments using UpdateEventArgsSchema and calls the handleUpdateEvent function for the update_event tool.
    case "update_event": {
      const validatedArgs = UpdateEventArgsSchema.parse(args);
      return await handleUpdateEvent(validatedArgs);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation (implying mutation) but doesn't describe what happens with partial updates, whether changes are reversible, permission requirements, rate limits, or error conditions. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that states the core purpose without unnecessary words. It's front-loaded with the essential information and has zero wasted content, making it easy for an agent to parse quickly.

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 8 parameters, nested objects, no annotations, and no output schema, the description is insufficient. It doesn't address behavioral aspects like partial updates, error handling, or return values, leaving the agent with incomplete context for proper tool invocation.

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?

The schema has 75% description coverage, providing good documentation for most parameters. The description adds no parameter-specific information beyond what's in the schema, so it doesn't compensate for the 25% gap (e.g., attendees object properties lack descriptions). With high schema coverage, the baseline of 3 is appropriate as the description doesn't enhance parameter understanding.

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 action ('Update') and resource ('existing event in Google Calendar'), making the purpose immediately understandable. It distinguishes this as an update operation rather than creation or deletion, though it doesn't explicitly contrast with sibling tools like create_event or delete_event beyond the verb choice.

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 doesn't mention prerequisites (e.g., needing an existing event ID), constraints, or typical use cases, leaving the agent to infer usage from the tool 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

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/peadams21/Google-Calendar-MCP-Server'

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