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

List Spaces

list_spaces

Read-onlyIdempotent

Lists Google Chat spaces, including rooms and direct messages, accessible to the specified user so you can identify available chats.

Instructions

Lists Google Chat spaces (rooms and direct messages) accessible to the user.

Input Schema

Name	Required	Default
`page_size`	No
`space_type`	No	all
`user_google_email`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.0.1Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / page_size / title
```
Removed value: -"Page Size"
```

removedInput schema / properties / service

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

removedInput schema / properties / space_type / title
```
Removed value: -"Space Type"
```
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_spacesArguments"
```

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the useful 'accessible to the user' scope constraint, but is silent on pagination behavior despite a page_size default of 100 (no mention of page tokens or how many results come back).

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?

A single front-loaded sentence with no wasted words; scope and access constraint come first. It is appropriately tight, though the brevity leaves the noted gaps rather than using a second short sentence to close them.

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?

An output schema exists and annotations cover the safety profile, so return format needn't be spelled out. However, for a paginated, filterable listing tool with zero schema descriptions, the description should at least indicate pagination and the space_type options; those omissions are meaningful gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so all three parameters rely on the description, which explains none of them explicitly. The phrase 'rooms and direct messages' hints at the space_type values and 'accessible to the user' hints at user_google_email, but page_size and the accepted space_type strings remain undocumented.

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 (lists) and resource (Google Chat spaces), and clarifies the scope by defining spaces as 'rooms and direct messages' plus the accessibility constraint. It is distinguishable from chat siblings like get_messages or search_messages, though it does not explicitly contrast with them.

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?

Usage is only implied: an agent can infer this is a discovery tool to enumerate spaces before calling get_messages or send_message, but the description never states when to use it or what alternatives exist for finding a space (e.g., search).

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

Deploy Server