Skip to main content
Glama
ricleedo

Google Services MCP Server

by ricleedo

calendar-create-event

Add new events to Google Calendar with title, time, location, and attendees. Schedule meetings and appointments directly from the Google Services MCP Server.

Instructions

Create a new calendar event. Current time: 1/3/2026, 11:25:51 AM

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesEvent title/summary
descriptionNoEvent description
locationNoEvent location
startDateTimeYesStart date/time in ISO format (e.g., '2025-01-15T09:00:00-07:00')
endDateTimeYesEnd date/time in ISO format (e.g., '2025-01-15T10:00:00-07:00')
attendeesNoArray of attendee email addresses
calendarIdNoCalendar ID - Available options: 'primary' (Primary Calendar)primary
timeZoneNoTime zone - defaults to local time (UTC). Examples: 'America/New_York', 'Europe/London', 'Asia/Tokyo'

Implementation Reference

  • The core handler function that implements the calendar event creation logic using Google Calendar API. It constructs the event object, inserts it via the API, handles attendees, and returns a formatted Markdown response.
    export async function createEvent(
      params: z.infer<ReturnType<typeof createEventSchema>>
    ) {
      try {
        const auth = createCalendarAuth();
        const calendar = google.calendar({ version: "v3", auth });
    
        const event: any = {
          summary: params.summary,
          description: params.description,
          location: params.location,
          start: {
            dateTime: params.startDateTime,
            timeZone: params.timeZone,
          },
          end: {
            dateTime: params.endDateTime,
            timeZone: params.timeZone,
          },
        };
    
        if (params.attendees && params.attendees.length > 0) {
          event.attendees = params.attendees.map((email) => ({ email }));
        }
    
        const response = await calendar.events.insert({
          calendarId: params.calendarId,
          requestBody: event,
          sendUpdates: "all", // Send invitations to attendees
        });
    
        const eventData = {
          id: response.data.id,
          summary: response.data.summary,
          start: response.data.start,
          end: response.data.end,
          location: response.data.location,
          description: response.data.description,
          attendees: response.data.attendees,
          htmlLink: response.data.htmlLink,
        };
    
        return {
          content: [
            {
              type: "text" as const,
              text: `# Event Created Successfully ✅\n\n${formatEventToMarkdown(eventData)}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error creating event: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters for the createEvent tool, including event details, attendees, calendar ID, and time zone.
    export const createEventSchema = () =>
      z.object({
        summary: z.string().describe("Event title/summary"),
        description: z.string().optional().describe("Event description"),
        location: z.string().optional().describe("Event location"),
        startDateTime: z
          .string()
          .describe(
            "Start date/time in ISO format (e.g., '2025-01-15T09:00:00-07:00')"
          ),
        endDateTime: z
          .string()
          .describe(
            "End date/time in ISO format (e.g., '2025-01-15T10:00:00-07:00')"
          ),
        attendees: z
          .array(z.string())
          .optional()
          .describe("Array of attendee email addresses"),
        calendarId: z
          .string()
          .default("primary")
          .describe(getCalendarDescription()),
        timeZone: z
          .string()
          .optional()
          .describe(
            `Time zone - defaults to local time (${systemTimezone}). Examples: 'America/New_York', 'Europe/London', 'Asia/Tokyo'`
          ),
      });
  • src/index.ts:215-222 (registration)
    MCP server tool registration for 'calendar-create-event', specifying name, description, input schema from createEventSchema, and handler wrapper calling createEvent.
    server.tool(
      "calendar-create-event",
      "Create a new calendar event. Current time: " + new Date().toLocaleString(),
      createEventSchema().shape,
      async (params) => {
        return await createEvent(params);
      }
    );
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 the action ('Create a new calendar event') but fails to mention critical behavioral aspects: whether this requires authentication, what permissions are needed, if it's idempotent, what happens on failure, or what the response contains. The timestamp is irrelevant behavioral noise.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is stated in the first clause, but the timestamp ('Current time: 1/3/2026, 11:25:51 AM') adds unnecessary length without value. While brief, this irrelevant information prevents a higher score for true conciseness.

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 no annotations and no output schema, the description is inadequate. It doesn't explain what happens after creation (e.g., returns event ID), error conditions, authentication requirements, or how it differs from sibling tools. The timestamp adds no relevant context for 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?

Schema description coverage is 100%, so the schema fully documents all 8 parameters with clear descriptions, formats, and defaults. The description adds no parameter information beyond what's in the schema, meeting the baseline score of 3 when schema coverage is high.

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 ('Create') and resource ('new calendar event'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'calendar-update-event' beyond the basic action, and the timestamp inclusion ('Current time: 1/3/2026, 11:25:51 AM') is irrelevant clutter that doesn't enhance purpose clarity.

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 'calendar-update-event' or 'calendar-list-events'. The description lacks any context about prerequisites, appropriate scenarios, or exclusions, leaving the agent to infer usage solely from the tool name and schema.

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/ricleedo/Google-Service-MCP'

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