grr

Overview Schema Source Related Servers Discussions Admin

chat.spaces.members.patch

Updates a Google Chat space membership by applying a field mask to change the member's role.

Instructions

Updates a membership. For an example, see Update a user's membership in a space. Supports the following types of authentication: - App authentication with administrator approval and the authorization scope: - https://www.googleapis.com/auth/chat.app.memberships (only in spaces the app created) - [User authentication](https://developer [HTTP PATCH] — updates the resource; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON Membership object accepting affiliation, createTime, deleteTime, groupMember, member, name, role, state; pass it via params or whole via body_file Siblings over the same resource: create, delete, get, list.

Input Schema

Name	Required	Description
`name`	Yes	[URL path segment] Identifier. Resource name of the membership, assigned by the server. Format: `spaces/{space}/members/{member}`
`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. The body is a JSON Membership object.
`updateMask`	No	[query parameter] Required. The field paths to update. Separate multiple values with commas or use `*` to update all field paths. Currently supported field paths: - `role`
`request_body`	No	Request body of type Membership: pass it via `params` (merged into the built body) or whole via `body_file`.
`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.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / body_file / description

Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON Membership object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type Membership: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "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"
+}

Changed6 schema fields changedOct 26, 2026

changedInput schema / properties / name / description

Previous value: -"Identifier. Resource name of the membership, assigned by the server. Format: `spaces/{space}/members/{member}`"New value: +"[URL path segment] Identifier. Resource name of the membership, assigned by the server. Format: `spaces/{space}/members/{member}`"

addedInput schema / properties / name / pattern

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

changedInput schema / properties / updateMask / description

Previous value: -"Required. The field paths to update. Separate multiple values with commas or use `*` to update all field paths. Currently supported field paths: - `role`"New value: +"[query parameter] Required. The field paths to update. Separate multiple values with commas or use `*` to update all field paths. Currently supported field paths: - `role`"

addedInput schema / properties / updateMask / format
```
Added value: +"google-fieldmask"
```

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

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose the mutating PATCH behavior, refusal under readonly safety profiles, returned JSON resource, authentication modes, and request-body handling. It loses a point because the user-authentication detail is truncated and the authorization requirements are only partially spelled out.

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 description is dense and begins with the purpose, but it becomes a run-on paragraph mixing documentation links, truncated auth text, HTTP method notes, return behavior, body fields, and siblings. It is not wasteful in content, but its structure and truncation reduce readability.

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?

For a mutation tool with 8 parameters, nested request body, no annotations, and an output schema, the description supplies the important behavioral context: mutation semantics, safety-profile refusal, auth modes, body handling, and sibling resources. The main omissions are the truncated auth detail and the updateMask limitation, which is covered in the schema.

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 schema already explains the parameters, including the required updateMask and useAdminAccess. The description restates the body fields and params/body_file mechanism, but adds little semantic meaning beyond the structured schema.

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 first sentence, "Updates a membership," states a specific verb and resource, and the later list of sibling operations on the same resource (create, delete, get, list) makes the tool's role distinguishable. The subsequent body-field list further clarifies what kinds of updates are in scope.

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 description names sibling operations over the same resource and notes that HTTP PATCH updates the resource, but it never explicitly states when to choose patch versus create/delete/get/list. The readonly safety-profile refusal is useful context, but conditional alternative guidance is only implied.

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

Deploy Server