Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

List Calendars

list_calendars

Read-onlyIdempotent

Lists calendars accessible to a Google user, returning paginated results for easy browsing and selection.

Instructions

Retrieves a list of calendars accessible to the authenticated user.

Input Schema

TableJSON Schema

Name	Required	Description
`page_token`	No	Token for the next page, taken from a previous response.
`max_results`	No	Maximum calendars to return in one page. Omit to use the API default.
`user_google_email`	Yes	The user's Google email address. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.28.0Sep 24, 2026
- removedInput schema / properties / max_results / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / max_results / type
```
Added value: +"integer"
```
- removedInput schema / properties / page_token / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / page_token / type
```
Added value: +"string"
```

Changed2 schema fields changedv1.26.0Sep 6, 2026

addedInput schema / properties / max_results

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Maximum calendars to return in one page. Omit to use the API default."
+}

addedInput schema / properties / page_token

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Token for the next page, taken from a previous response."
+}

Changed7 schema fields changedv1.0.1Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / service

Removed value: -{
-  "title": "service",
-  "type": "string"
-}

addedInput schema / properties / user_google_email / description
```
Added value: +"The user's Google email address. Required."
```
removedInput schema / properties / user_google_email / title
```
Removed value: -"User Google Email"
```

changedInput schema / required

Previous value: -[
-  "service",
-  "user_google_email"
-]New value: +[
+  "user_google_email"
+]

removedInput schema / title

Removed value: -"list_calendarsArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv1.0.0Jun 10, 2025

TDQS

A3.7/5.0

Behavior3/5

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

The annotations already declare read-only, idempotent, and non-destructive behavior, and the description confirms this with 'Retrieves'. It adds the useful scoping detail that results are limited to calendars accessible to the authenticated user, but it does not provide richer behavioral context such as pagination behavior or response limitations.

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 a single sentence that front-loads the verb and object with no filler or redundant restatement of the title. Every word carries meaningful information.

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?

For a simple read-only list tool with full schema coverage, strong annotations, and an output schema, the description covers everything needed for correct invocation. It does not need to explain return values or parameter details because those are supplied by structured context.

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%, and the schema adequately documents user_google_email, page_token, and max_results. The description adds no additional parameter-level meaning, so the 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?

The description states a concrete verb-resource pair, 'Retrieves a list of calendars', and scopes the result to the authenticated user, which makes it distinct from calendar mutation tools like create_calendar. It does not explicitly name or differentiate a sibling, so it falls slightly short of the top rating.

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

Usage Guidelines3/5

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

The intended use is implied: call this when a list of calendars a user can access is needed, rather than when creating or managing calendar data. There is no explicit statement about when to prefer it over siblings such as get_events or create_calendar, so the agent must infer the selection context.

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

Deploy Server