grr

Overview Schema Source Related Servers Discussions Admin

chat.spaces.members.get

Fetches details about a specific membership in a Google Chat space by resource name, so you can inspect member roles and status.

Instructions

Returns details about a membership. For an example, see Get details about a user's or Google Chat app's membership. Supports the following types of authentication: - App authentication with one of the following authorization scopes: - https://www.googleapis.com/auth/chat.bot - https://www.googleapis.com/auth/chat.app.memberships (requires [administrator approval](https://support.goo [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, list, patch.

Input Schema

Name	Required	Description
`name`	Yes	[URL path segment] Required. Resource name of the membership to retrieve. To get the app's own membership [by using user authentication](https://developers.google.com/workspace/ch
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`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
`name`	No
`role`	No
`state`	No
`member`	No
`createTime`	No
`deleteTime`	No
`affiliation`	No
`groupMember`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026

changedInput schema / properties / name / description

Previous value: -"Required. Resource name of the membership to retrieve. To get the app's own membership [by using user authentication](https://developers.google.com/workspace/ch"New value: +"[URL path segment] Required. Resource name of the membership to retrieve. To get the app's own membership [by using user authentication](https://developers.google.com/workspace/ch"

addedInput schema / properties / name / pattern

Added value: +"^spaces/[^/]+/members/[^/]+$"

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": {
+    "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"
+}

First observedOct 26, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full load. It does add genuinely useful behavioral context the schema lacks: the authentication types, the specific OAuth scopes, and the administrator-approval requirement for `chat.app.memberships`. However, the boilerplate about request bodies being built from parameters or read from `body_file` is misleading for a GET endpoint and no error semantics (403/404, membership visibility) are described.

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 purpose is correctly front-loaded in the first sentence. But the body is dominated by long authorization URLs and generic transport boilerplate, including `body_file`/request-body text that has no application to a GET call, which dilutes the useful content.

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, so return values need no explanation, and the required `name` is well documented. What is missing is the operational context for a conditional-access read: how results differ under app vs. user auth and admin access, and what failure modes to expect. Adequate but with clear gaps.

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 the baseline of 3 applies. The description adds only one semantic detail beyond the schema - that typed parameters win over the `params` map - while the meaning of `name` and `useAdminAccess` is already fully documented in the schema itself.

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 first sentence states a specific verb and resource: 'Returns details about a membership.' The trailing note enumerating siblings over the same resource (create, delete, list, patch) lets an agent separate this from the other membership operations. It only falls short of a 5 because 'a membership' is generic - it never says Chat space membership explicitly in the purpose sentence, leaning on the tool name for that.

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 sibling list implies this is the single-resource read versus list/create/delete/patch, and the required `name` pattern signals a lookup-by-identifier flow. But there is no explicit 'use this when you already have the resource name; use list to discover names' guidance, and no exclusions or prerequisites stated.

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

Deploy Server