grr

Overview Schema Source Related Servers Discussions Admin

people.contactGroups.list

List all contact groups owned by the authenticated user to review group names, metadata, and member counts without fetching members. Supports pagination and sync tokens for retrieving changed groups.

Instructions

List all contact groups owned by the authenticated user. Members of the contact groups are not populated [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: batchGet, create, delete, get, update.

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.
`dry_run`	No	Return the request that would be sent, without sending it.
`pageSize`	No	[query parameter] Optional. The maximum number of resources to return. Valid values are between 1 and 1000, inclusive. Defaults to 30 if not set or set to 0.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`pageToken`	No	[query parameter] Optional. The next_page_token value returned from a previous call to [ListContactGroups](/people/api/rest/v1/contactgroups/list). Requests the next page of reso
`syncToken`	No	[query parameter] Optional. A sync token, returned by a previous call to `contactgroups.list`. Only resources changed since the sync token was created will be returned.
`groupFields`	No	[query parameter] Optional. A field mask to restrict which fields on the group are returned. Defaults to `metadata`, `groupType`, `memberCount`, and `name` if not set or set to e

Output Schema

Name	Required	Description	Default
`totalItems`	No
`contactGroups`	No
`nextPageToken`	No
`nextSyncToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 26, 2026

changedInput schema / properties / groupFields / description

Previous value: -"Optional. A field mask to restrict which fields on the group are returned. Defaults to `metadata`, `groupType`, `memberCount`, and `name` if not set or set to e"New value: +"[query parameter] Optional. A field mask to restrict which fields on the group are returned. Defaults to `metadata`, `groupType`, `memberCount`, and `name` if not set or set to e"

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

changedInput schema / properties / pageSize / description

Previous value: -"Optional. The maximum number of resources to return. Valid values are between 1 and 1000, inclusive. Defaults to 30 if not set or set to 0."New value: +"[query parameter] Optional. The maximum number of resources to return. Valid values are between 1 and 1000, inclusive. Defaults to 30 if not set or set to 0."

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

changedInput schema / properties / pageToken / description

Previous value: -"Optional. The next_page_token value returned from a previous call to [ListContactGroups](/people/api/rest/v1/contactgroups/list). Requests the next page of reso"New value: +"[query parameter] Optional. The next_page_token value returned from a previous call to [ListContactGroups](/people/api/rest/v1/contactgroups/list). Requests the next page of reso"

changedInput schema / properties / syncToken / description

Previous value: -"Optional. A sync token, returned by a previous call to `contactgroups.list`. Only resources changed since the sync token was created will be returned."New value: +"[query parameter] Optional. A sync token, returned by a previous call to `contactgroups.list`. Only resources changed since the sync token was created will be returned."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "contactGroups": {
+      "items": {
+        "properties": {
+          "clientData": {
+            "items": {
+              "properties": {
+                "key": {
+                  "type": "string"
+                },
+                "value": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "etag": {
+            "type": "string"
+          },
+          "formattedName": {
+            "type": "string"
+          },
+          "groupType": {
+            "enum": [
+              "GROUP_TYPE_UNSPECIFIED",
+              "USER_CONTACT_GROUP",
+              "SYSTEM_CONTACT_GROUP"
+            ],
+            "type": "string"
+          },
+          "memberCount": {
+            "type": "integer"
+          },
+          "memberResourceNames": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "metadata": {
+            "properties": {
+              "deleted": {
+                "type": "boolean"
+              },
+              "updateTime": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "name": {
+            "type": "string"
+          },
+          "resourceName": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextPageToken": {
+      "type": "string"
+    },
+    "nextSyncToken": {
+      "type": "string"
+    },
+    "totalItems": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the HTTP GET method, the owned-groups scope, and that members are not populated, but it does not state read-only safety explicitly, auth requirements, pagination behavior, or rate limits.

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 and member-omission facts are front-loaded, which is good. However, the generic sentence about request bodies, typed flags, and body_file is boilerplate for a GET list operation and makes the definition less concise and potentially confusing.

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 list operation with a rich schema and an output schema, the description covers the key scope and the important caveat that members are not populated. It is mostly complete, though it could clarify pagination and sync behavior at a high level rather than relying entirely on 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 baseline is 3. The description adds only generic request-building context about typed parameters, params, and body_file, but does not add meaning beyond the schema for pageSize, pageToken, syncToken, or groupFields.

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 description states a specific verb and resource: list all contact groups owned by the authenticated user, and notes that members are not populated. It also names sibling operations over the same resource, though it does not explain how to choose among them.

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 implies usage by saying it lists all owned contact groups and that members are not populated, but it gives no explicit when-to-use guidance or when-not-to-use exclusions. Siblings such as batchGet and get are named, but the conditions selecting list over them are not stated.

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

Deploy Server