gcal

create_event

Create a new calendar event. Use this to schedule meetings, appointments, or all-day events. For all-day events, only provide dates (end date is EXCLUSIVE - use '2024-01-16' for a single day event on Jan 15). For timed events, both start and end times are required. Can optionally invite attendees with email notifications. The created event ID can be used for future updates or deletion.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`endDate`	Yes	End date YYYY-MM-DD. For all-day: next day. For timed: same or later day
`endTime`	No	End time HH:MM:SS (e.g., "15:00:00"). Required if startTime provided
`summary`	Yes	Event title
`location`	No	Event location (address or meeting room)
`timeZone`	Yes	Timezone (e.g., "America/Los_Angeles", "UTC", "Europe/London")
`attendees`	No	Email addresses of attendees to invite
`startDate`	Yes	Start date YYYY-MM-DD (e.g., "2024-01-15")
`startTime`	No	Start time HH:MM:SS (e.g., "14:00:00"). Omit for all-day events
`calendarId`	Yes	Calendar ID from list_calendars (required - get ID first using list_calendars)
`description`	No	Event description. Supports markdown formatting
`sendUpdates`	No	all: notify everyone, externalOnly: only external users, none: no notifications	all

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`end`	Yes
`start`	Yes
`status`	No
`summary`	Yes
`htmlLink`	No
`location`	No
`attendees`	No
`description`	No
`hangoutLink`	No
`conferenceData`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedApr 18, 2026

addedOutput schema / properties / conferenceData

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "conferenceId": {
+      "type": "string"
+    },
+    "conferenceSolution": {
+      "additionalProperties": false,
+      "properties": {
+        "iconUri": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "entryPoints": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "entryPointType": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "uri": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "entryPointType",
+          "uri"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / hangoutLink
```
Added value: +{
+  "type": "string"
+}
```

Changed8 schema fields changedApr 7, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedOutput schema / properties / attendees / items / properties / responseStatus / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / attendees / items / properties / responseStatus / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- removedOutput schema / properties / end / $ref
```
Removed value: -"#/properties/start"
```
- addedOutput schema / properties / end / additionalProperties
```
Added value: +false
```
- addedOutput schema / properties / end / properties
```
Added value: +{
+  "date": {
+    "type": "string"
+  },
+  "dayOfWeek": {
+    "type": "string"
+  },
+  "time": {
+    "type": "string"
+  },
+  "timezone": {
+    "type": "string"
+  }
+}
```
- addedOutput schema / properties / end / required
```
Added value: +[
+  "date",
+  "dayOfWeek"
+]
```
- addedOutput schema / properties / end / type
```
Added value: +"object"
```

Changed1 schema field changedFeb 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "attendees": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "email": {
+            "type": "string"
+          },
+          "responseStatus": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "email"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "description": {
+      "type": "string"
+    },
+    "end": {
+      "$ref": "#/properties/start"
+    },
+    "htmlLink": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "location": {
+      "type": "string"
+    },
+    "start": {
+      "additionalProperties": false,
+      "properties": {
+        "date": {
+          "type": "string"
+        },
+        "dayOfWeek": {
+          "type": "string"
+        },
+        "time": {
+          "type": "string"
+        },
+        "timezone": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "date",
+        "dayOfWeek"
+      ],
+      "type": "object"
+    },
+    "status": {
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "summary",
+    "start",
+    "end"
+  ],
+  "type": "object"
+}

First observedJan 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), description discloses key behaviors: all-day events only need dates, timed events require both start and end times, attendee invitations possible, and sendUpdates controls notifications. No contradictions with annotations.

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

Conciseness4/5

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

Description is a single paragraph with clear front-loading of purpose. It is well-organized but slightly lengthy; still every sentence adds value, so minor deduction for potential slight wordiness.

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

Completeness5/5

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

Given 11 parameters, 100% schema coverage, and an output schema, the description covers all essential aspects: purpose, use-case differentiation, parameter behavior, edge cases, and inter-tool dependencies. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, description adds critical semantics: clarifies that endDate for all-day is exclusive ('use '2024-01-16' for a single day on Jan 15'), explains that startTime is omitted for all-day events, and specifies that calendarId comes from list_calendars. This goes beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states 'Create a new calendar event' and lists specific use cases (meetings, appointments, all-day events). It clearly distinguishes from sibling tools like update_event and delete_event by mentioning the returned event ID for future updates/deletions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides detailed usage guidance: when to use all-day vs timed events, required fields for each case, and the exclusive end date nuance. Also links to list_calendars for obtaining calendarId and notes that created ID enables future operations.

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

All gcal tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.