Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

calendar_events_insert

Create a new Google Calendar event with a title, start and end times, location, description, and attendees. Add invitees and optionally send invitation emails in one operation.

Instructions

Create a new calendar event.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "calendarId": "<calendarId>",
      "summary": "<summary>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "calendar_events_insert"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd time JSON
startYesStart time JSON (e.g. '{"dateTime":"2026-03-10T10:00:00-07:00"}')
summaryYesEvent title
locationNoEvent location
attendeesNoAttendees (JSON array as string, e.g. '[{"email":"a@x.com"},{"email":"b@x.com","optional":true}]')
calendarIdYesCalendar ID
descriptionNoEvent description
sendUpdatesNoSends invitation email to attendees when set: "all", "externalOnly", or "none" (default: none — no email, though the event may still appear on an attendee's calendar depending on their settings)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv0.4.1
    • addedInput schema / properties / attendees
      Added value: +{
      +  "description": "Attendees (JSON array as string, e.g. '[{\"email\":\"a@x.com\"},{\"email\":\"b@x.com\",\"optional\":true}]')",
      +  "type": "string"
      +}
    • addedInput schema / properties / sendUpdates
      Added value: +{
      +  "description": "Sends invitation email to attendees when set: \"all\", \"externalOnly\", or \"none\" (default: none — no email, though the event may still appear on an attendee's calendar depending on their settings)",
      +  "enum": [
      +    "all",
      +    "externalOnly",
      +    "none"
      +  ],
      +  "type": "string"
      +}
  3. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the write and non-idempotent nature is covered by structured data rather than the description. The description adds nothing beyond that, such as whether invitations are emailed, whether duplicate events are created on retry, or what permissions are required.

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?

A single short sentence with no waste, but it is front-loaded with nothing useful and is arguably under-specified for an 8-parameter mutation tool. Brevity here reflects thinness rather than efficiency.

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 non-idempotent, open-world mutation with 8 parameters (4 required) and no output schema, the description omits key facts: invitation-email behavior via sendUpdates, required-field expectations, and whether only calendarId/summary/start/end must be supplied. It is not complete enough to call the tool confidently without reading the schema.

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%, including the sendUpdates enum's email semantics and JSON-formatted start/end/attendees strings, so the schema carries the parameter burden. The description adds no meaning beyond it; baseline 3 applies.

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?

States a specific verb (create) and resource (calendar event), which distinguishes it from the get/list/update/delete siblings by operation. It stops short of differentiating itself from other insert tools or describing scope (single event vs. recurring, which calendar).

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 on when to use this versus calendar_events_update or other insertion tools, and no mention of prerequisites such as write access to the target calendar or the need for a valid calendarId. The agent must infer all usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.