grr

Overview Schema Source Related Servers Discussions Admin

chat.spaces.members.delete

Removes a user or Chat app membership from a Google Chat space, enabling administrators to revoke access and clean up membership records.

Instructions

Deletes a membership. For an example, see Remove a user or a Google Chat app from 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 - [User authentication](https://developers.google.com/workspace/ [HTTP DELETE] — removes the resource; irreversible unless the API documents a trash/undo flow; refused under --readonly safety profiles. Returns the post-delete resource state (or empty) 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, get, list, patch.

Input Schema

Name	Required	Description
`name`	Yes	[URL path segment] Required. Resource name of the membership to delete. Chat apps can delete human users' or their own memberships. Chat apps can't delete other apps' memberships.
`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 delete. Chat apps can delete human users' or their own memberships. Chat apps can't delete other apps' memberships."New value: +"[URL path segment] Required. Resource name of the membership to delete. Chat apps can delete human users' or their own memberships. Chat apps can't delete other apps' memberships."

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

A4/5.0

Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the HTTP DELETE method, irreversibility ("irreversible unless the API documents a trash/undo flow"), the readonly-profile refusal, and that the post-delete resource state is returned as JSON. The authentication paragraph is truncated mid-sentence, leaving the user-auth scope list incomplete.

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 critical facts (delete, irreversible, returns post-delete state, siblings) are front-loaded, but the pasted Google documentation links and the mangled truncation of the user-authentication bullet add noise without earning their place.

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 an output schema and full param coverage, the description supplies what the structured fields can't: irreversibility, auth/admin approval requirements, and the sibling map. Only the truncated auth text leaves a small gap.

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 `name` pattern, the app-vs-human membership restriction, and the query/util params (dry_run, body_file, params) are already documented in the schema. The description adds no parameter-level detail beyond the auth scopes, so the baseline 3 applies.

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+resource ("Deletes a membership") and explicitly enumerates the sibling operations over the same resource (create, get, list, patch), so the agent can distinguish create/get/list/patch without opening another 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?

Gives real call prerequisites — app authentication with administrator approval and the chat.app.memberships scope, or user authentication — plus a clear when-not signal ("refused under --readonly safety profiles"). It doesn't discuss when to prefer patch over delete or what happens to the space itself, so not a full 5.

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

Deploy Server