grr

Overview Schema Source Related Servers Discussions Admin

chat.spaces.members.list

Lists memberships in a Google Chat space, enabling you to retrieve and paginate space members, invited users, and group memberships.

Instructions

Lists memberships in a space. For an example, see List users and Google Chat apps in a space. Listing memberships with app authentication lists memberships in spaces that the Chat app has access to, but excludes Chat app memberships, including its own. Listing memberships with User authentication lists memberships in spaces that the authenticated user has access to. Supports [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: create, delete, get, patch.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`filter`	No	[query parameter] Optional. A query filter. You can filter memberships by a member's role ([`role`](https://developers.google.com/workspace/chat/api/reference/rest/v1/spaces.memb
`params`	No	Parameter map merged into the request; typed parameters win.
`parent`	Yes	[URL path segment] Required. The resource name of the space for which to fetch a membership list. Format: spaces/{space}
`dry_run`	No	Return the request that would be sent, without sending it.
`pageSize`	No	[query parameter] Optional. The maximum number of memberships to return. The service might return fewer than this value. If unspecified, at most 100 memberships are returned. The
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`pageToken`	No	[query parameter] Optional. A page token, received from a previous call to list memberships. Provide this parameter to retrieve the subsequent page. When paginating, all other pa
`showGroups`	No	[query parameter] Optional. When `true`, also returns memberships associated with a Google Group, in addition to other types of memberships. If a filter is set, Google Group memb
`showInvited`	No	[query parameter] Optional. When `true`, also returns memberships associated with invited members, in addition to other types of memberships. If a filter is set, invited membersh
`useAdminAccess`	No	[query parameter] Optional. When `true`, the method runs using the user's Google Workspace administrator privileges. The calling user must be a Google Workspace administrator wit

Output Schema

Name	Required	Description	Default
`memberships`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 26, 2026

changedInput schema / properties / filter / description

Previous value: -"Optional. A query filter. You can filter memberships by a member's role ([`role`](https://developers.google.com/workspace/chat/api/reference/rest/v1/spaces.memb"New value: +"[query parameter] Optional. A query filter. You can filter memberships by a member's role ([`role`](https://developers.google.com/workspace/chat/api/reference/rest/v1/spaces.memb"

changedInput schema / properties / pageSize / description

Previous value: -"Optional. The maximum number of memberships to return. The service might return fewer than this value. If unspecified, at most 100 memberships are returned. The"New value: +"[query parameter] Optional. The maximum number of memberships to return. The service might return fewer than this value. If unspecified, at most 100 memberships are returned. The"

addedInput schema / properties / pageSize / format
```
Added value: +"int32"
```

changedInput schema / properties / pageToken / description

Previous value: -"Optional. A page token, received from a previous call to list memberships. Provide this parameter to retrieve the subsequent page. When paginating, all other pa"New value: +"[query parameter] Optional. A page token, received from a previous call to list memberships. Provide this parameter to retrieve the subsequent page. When paginating, all other pa"

changedInput schema / properties / parent / description

Previous value: -"Required. The resource name of the space for which to fetch a membership list. Format: spaces/{space}"New value: +"[URL path segment] Required. The resource name of the space for which to fetch a membership list. Format: spaces/{space}"

addedInput schema / properties / parent / pattern
```
Added value: +"^spaces/[^/]+$"
```

changedInput schema / properties / showGroups / description

Previous value: -"Optional. When `true`, also returns memberships associated with a Google Group, in addition to other types of memberships. If a filter is set, Google Group memb"New value: +"[query parameter] Optional. When `true`, also returns memberships associated with a Google Group, in addition to other types of memberships. If a filter is set, Google Group memb"

changedInput schema / properties / showInvited / description

Previous value: -"Optional. When `true`, also returns memberships associated with invited members, in addition to other types of memberships. If a filter is set, invited membersh"New value: +"[query parameter] Optional. When `true`, also returns memberships associated with invited members, in addition to other types of memberships. If a filter is set, invited membersh"

changedInput schema / properties / useAdminAccess / description

Previous value: -"Optional. When `true`, the method runs using the user's Google Workspace administrator privileges. The calling user must be a Google Workspace administrator wit"New value: +"[query parameter] Optional. When `true`, the method runs using the user's Google Workspace administrator privileges. The calling user must be a Google Workspace administrator wit"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "memberships": {
+      "items": {
+        "properties": {
+          "affiliation": {
+            "enum": [
+              "AFFILIATION_UNSPECIFIED",
+              "INTERNAL",
+              "EXTERNAL",
+              "MANAGED_EXTERNAL"
+            ],
+            "type": "string"
+          },
+          "createTime": {
+            "type": "string"
+          },
+          "deleteTime": {
+            "type": "string"
+          },
+          "groupMember": {
+            "properties": {
+              "name": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "member": {
+            "properties": {
+              "avatarUrl": {
+                "type": "string"
+              },
+              "displayName": {
+                "type": "string"
+              },
+              "domainId": {
+                "type": "string"
+              },
+              "email": {
+                "type": "string"
+              },
+              "isAnonymous": {
+                "type": "boolean"
+              },
+              "name": {
+                "type": "string"
+              },
+              "type": {
+                "enum": [
+                  "TYPE_UNSPECIFIED",
+                  "HUMAN",
+                  "BOT"
+                ],
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "name": {
+            "type": "string"
+          },
+          "role": {
+            "enum": [
+              "MEMBERSHIP_ROLE_UNSPECIFIED",
+              "ROLE_MEMBER",
+              "ROLE_MANAGER",
+              "ROLE_ASSISTANT_MANAGER"
+            ],
+            "type": "string"
+          },
+          "state": {
+            "enum": [
+              "MEMBERSHIP_STATE_UNSPECIFIED",
+              "JOINED",
+              "INVITED",
+              "NOT_A_MEMBER"
+            ],
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextPageToken": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it declares the operation is an HTTP GET (read-only), discloses that app-auth results silently omit Chat app memberships including the app's own, and explains how request bodies are sourced from typed parameters vs `params` vs `body_file`. Missing quota/rate-limit or pagination caveats, but the auth-mode exclusion behavior is the key non-obvious trait and it is stated.

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

Conciseness3/5

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

The core statement is front-loaded, but the boilerplate block ("Supports [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters...") is largely irrelevant to a GET list call and reads as template filler. The example link and auth-mode paragraphs earn their place; the plumbing paragraph does not.

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?

An output schema exists so return values need not be described, and the description covers the operation, its auth-mode semantics, and the sibling set. For an 11-parameter list tool with 100% schema coverage, what remains is adequate; only quota/error behavior is unaddressed.

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%, so every parameter including filter, pageSize, pageToken, showGroups, showInvited and useAdminAccess is already documented in the schema. The description adds no parameter-level meaning beyond restating the params-map precedence and body_file mechanism that the schema itself describes.

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?

Opens with a specific verb plus resource ("Lists memberships in a space") and explicitly names the sibling operations over the same resource (create, delete, get, patch), so an agent can separate this from chat.spaces.members.get without opening a schema.

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 authentication-mode discussion tells the agent two concrete conditions under which behavior differs: app auth covers spaces the Chat app can access but excludes Chat app memberships, user auth covers what the authenticated user can access. It stops short of saying when to prefer this tool over chat.spaces.list or members.get, so no explicit exclusion set for those siblings.

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

Deploy Server