grr

Overview Schema Source Related Servers Discussions Admin

chat.spaces.members.create

Adds a user, Google Group, or calling Chat app as a member of a Google Chat space, inviting them when auto-accept is off or adding them directly otherwise.

Instructions

Creates a membership for the calling Chat app, a user, or a Google Group. Creating memberships for other Chat apps isn't supported. When creating a membership, if the specified member has their auto-accept policy turned off, then they're invited, and must accept the space invitation before joining. Otherwise, creating a membership adds the member directly to the specified space. Supports the following types of authentication: - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app [HTTP POST] — creates or triggers a change; 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: delete, get, list, patch.

Input Schema

Name	Required	Description
`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.
`parent`	Yes	[URL path segment] Required. The resource name of the space for which to create the membership. Format: spaces/{space}
`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.
`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"
+}

Changed4 schema fields changedOct 26, 2026

changedInput schema / properties / parent / description

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

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

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.2/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 load and does so well: it discloses HTTP POST semantics, that the call is refused under --readonly safety profiles, the invite-vs-direct-add side effect, the authentication requirement (link is truncated mid-URL), and that the response is the Membership resource. Missing are permission prerequisites beyond the admin query param and any rate-limit or idempotency notes.

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 behavioral and wrapper information is front-loaded, but the text is a run-on stack of copy-pasted API documentation plus appended CLI notes, and the authentication markdown link is broken and truncated mid-URL ('authenticate-authorize-chat-app [HTTP POST]'), leaving a malformed sentence. The field list (affiliation, createTime, deleteTime, ...) duplicates the schema.

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 mutating POST with a nested Membership body and an output schema, the description covers what an agent needs: who can be added, invite-vs-add behavior, auth mode, read-only refusal, body shape, and sibling operations. The remaining gaps are minor since the output schema documents the return value and the truncated auth link only costs detail, not correctness.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real value by resolving the overlapping body parameters: the request body is a JSON Membership object, its accepted fields are enumerated, and it can be passed via `params` or whole via `body_file`. That disambiguates `params` vs `request_body` vs `body_file`, which the schema alone leaves ambiguous.

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?

States a specific verb and resource ('Creates a membership') plus the scope of who can be a member (calling Chat app, a user, or a Google Group) and an explicit unsupported case (other Chat apps). It also names the sibling family over the same resource (delete, get, list, patch), so an agent can place it in the CRUD set without opening other schemas.

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?

Explains the two outcome paths clearly: if the member's auto-accept policy is off they are invited and must accept before joining, otherwise they are added directly. It also gives an exclusion ('Creating memberships for other Chat apps isn't supported') and points at the sibling delete/get/list/patch set, but does not compare against alternatives such as chat.spaces.setup or members.patch for changing an existing membership.

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

Deploy Server