Skip to main content
Glama
rishipradeep-think41

Google Workspace MCP Server

create_event

Schedule a new calendar event with title, start and end times, location, description, and attendee emails using the Google Workspace MCP Server.

Instructions

Create a new calendar event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attendeesNoList of attendee email addresses
descriptionNoEvent description
endYesEnd time in ISO format
locationNoEvent location
startYesStart time in ISO format
summaryYesEvent title

Implementation Reference

  • The handler function that creates a new calendar event by calling the Google Calendar API's events.insert method with the provided event details, handling errors appropriately.
    private async handleCreateEvent(args: any) {
      try {
        const {
          summary,
          location,
          description,
          start,
          end,
          attendees = [],
        } = args;
    
        const event = {
          summary,
          location,
          description,
          start: {
            dateTime: start,
            timeZone: Intl.DateTimeFormat().resolvedOptions().timeZone,
          },
          end: {
            dateTime: end,
            timeZone: Intl.DateTimeFormat().resolvedOptions().timeZone,
          },
          attendees: attendees.map((email: string) => ({ email })),
        };
    
        const response = await this.calendar.events.insert({
          calendarId: "primary",
          requestBody: event,
        });
    
        return {
          content: [
            {
              type: "text",
              text: `Event created successfully. Event ID: ${response.data.id}`,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: "text",
              text: `Error creating event: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
    
    private async handleUpdateEvent(args: any) {
  • The input schema and metadata (name, description) for the create_event tool, defining required and optional parameters for event creation.
    {
      name: "create_event",
      description: "Create a new calendar event",
      inputSchema: {
        type: "object",
        properties: {
          summary: {
            type: "string",
            description: "Event title",
          },
          location: {
            type: "string",
            description: "Event location",
          },
          description: {
            type: "string",
            description: "Event description",
          },
          start: {
            type: "string",
            description: "Start time in ISO format",
          },
          end: {
            type: "string",
            description: "End time in ISO format",
          },
          attendees: {
            type: "array",
            items: { type: "string" },
            description: "List of attendee email addresses",
          },
        },
        required: ["summary", "start", "end"],
      },
    },
  • src/index.ts:284-285 (registration)
    The switch case in the CallToolRequestHandler that registers and routes calls to the create_event handler.
    case "create_event":
      return await this.handleCreateEvent(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 for behavioral disclosure. While 'Create' implies a write operation, it doesn't mention permission requirements, whether the event becomes immediately visible to attendees, if notifications are sent, or what happens on validation errors. This leaves significant behavioral gaps for a mutation tool.

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 perfectly concise - a single sentence that states the core purpose without any wasted words. It's front-loaded with the essential information and doesn't include 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 no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation, what the return value might be, error conditions, or how this tool relates to its siblings. The agent would need to guess about important behavioral aspects.

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 description coverage is 100%, with all parameters well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured schema, so it meets the baseline expectation but doesn't provide extra value.

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 ('Create') and resource ('calendar event'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'update_event' or explain what distinguishes creation from modification in this context.

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 about when to use this tool versus alternatives like 'update_event' or 'list_events'. There's no mention of prerequisites, constraints, or typical use cases for creating versus modifying calendar events.

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