Skip to main content
Glama
conorbronsdon

Google Workspace (GWS) MCP Server

by conorbronsdon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

calendar_events_insert

Create a new calendar event with title, start/end times, location, attendees, and description. Send invitation emails to attendees when required.

Instructions

Create a new calendar event.

Input Schema

TableJSON 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. 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"
+}
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already indicate this is a mutating, non-idempotent, non-destructive operation. The description adds no further behavioral context such as invite email behavior, duplicate handling, or what the created event object contains.

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 one clear, front-loaded sentence with no filler or redundant information. It efficiently communicates the core operation.

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

Completeness3/5

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

The schema and annotations cover parameter semantics and mutation safety, making this minimally viable. However, there is no output schema and the description does not mention return values or usage context, leaving some gaps for an agent.

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%, with detailed parameter descriptions including JSON formats and enum meanings. The description itself adds no parameter-level meaning, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Create a new calendar event.' This clearly separates it from update/delete/list operations, though it does not explicitly name or contrast sibling tools.

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 given about when to use this tool versus calendar_events_update, calendar_events_delete, or calendar_events_list. There are no stated prerequisites or alternative conditions.

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

Deploy Server

Other Tools