gcal

get_calendar_events

Read-only

Retrieve events from a specific calendar within a time range. Use this to view scheduled events, check availability, or find specific appointments. Times are interpreted in the provided timezone. Without dateMax, returns all future events from dateMin. IMPORTANT: For single day events, use next day as dateMax (e.g., dateMin='2024-01-15' and dateMax='2024-01-16'). Event IDs from this tool are required for update/delete operations.

Input Schema

TableJSON Schema

Name	Required	Description
`dateMax`	No	End date YYYY-MM-DD. Events BEFORE this date. For single day, use next day
`dateMin`	Yes	Start date YYYY-MM-DD (e.g., "2024-01-15"). Required
`timeMax`	No	End time HH:MM:SS. Only valid with dateMax
`timeMin`	Yes	Start time HH:MM:SS (e.g., "09:00:00"). Required
`timeZone`	Yes	Timezone for interpreting dates/times (e.g., "America/Los_Angeles", "UTC")
`pageToken`	No	Pagination token from previous response
`calendarId`	Yes	Calendar ID from list_calendars (required - get ID first using list_calendars)
`maxResults`	No	Number of events to return (1-2500). Default: 10

Output Schema

TableJSON Schema

Name	Required	Description	Default
`events`	Yes
`message`	No
`calendarId`	Yes
`nextPageToken`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedApr 18, 2026

addedOutput schema / properties / events / items / 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 / events / items / properties / hangoutLink
```
Added value: +{
+  "type": "string"
+}
```

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

Changed1 schema field changedFeb 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "calendarId": {
+      "type": "string"
+    },
+    "events": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "attendees": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "email": {
+                  "type": "string"
+                },
+                "responseStatus": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "required": [
+                "email"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "description": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "end": {
+            "$ref": "#/properties/events/items/properties/start"
+          },
+          "htmlLink": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "location": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "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"
+          },
+          "updated": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "summary",
+          "start",
+          "end"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "type": "string"
+    },
+    "nextPageToken": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "calendarId",
+    "events",
+    "nextPageToken"
+  ],
+  "type": "object"
+}

First observedJan 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and non-destructive. The description adds behavioral details: timezone interpretation, default behavior without dateMax (returns all future events), and pagination via pageToken. 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?

The description is concise (5 sentences) and front-loaded with purpose. Every sentence adds value, including the note about event IDs. Slight improvement could be to remove redundancy with schema, but overall efficient.

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

Completeness4/5

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

Given the tool has an output schema, return value explanation is not needed. The description covers usage, parameters, timezone handling, pagination, and the important single-day event tip. Lacks mention of rate limits or error conditions, but these are not critical for a read-only tool.

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

Parameters4/5

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

Schema coverage is 100%; all parameters have descriptions. The description adds value by explaining calendarId source (list_calendars) and providing a usage note for dateMax. It also reinforces that timeMin and dateMin are required.

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?

The description uses a specific verb ('Retrieve events') and clearly identifies the resource ('from a specific calendar within a time range'). It distinguishes from sibling tools by stating it is for viewing, not creating/deleting/updating events.

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

Usage Guidelines4/5

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

The description provides clear context on when to use: 'view scheduled events, check availability, or find specific appointments'. It also includes an important note about single-day events and links event IDs to update/delete operations. Lacks explicit exclusion of alternatives like get_next_availability.

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.