grr

Overview Schema Source Related Servers Discussions Admin

people.contactGroups.get

Retrieves a specific contact group owned by the authenticated user using its resource name, returning the group details as JSON.

Instructions

Get a specific contact group owned by the authenticated user by specifying a contact group resource name [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, list, 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.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`maxMembers`	No	[query parameter] Optional. Specifies the maximum number of members to return. Defaults to 0 if not set, which will return zero members.
`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
`resourceName`	Yes	[URL path segment] Required. The resource name of the contact group to get.

Output Schema

Name	Required	Description	Default
`etag`	No
`name`	No
`metadata`	No
`groupType`	No
`clientData`	No
`memberCount`	No
`resourceName`	No
`formattedName`	No
`memberResourceNames`	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 / maxMembers / description

Previous value: -"Optional. Specifies the maximum number of members to return. Defaults to 0 if not set, which will return zero members."New value: +"[query parameter] Optional. Specifies the maximum number of members to return. Defaults to 0 if not set, which will return zero members."

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

changedInput schema / properties / resourceName / description

Previous value: -"Required. The resource name of the contact group to get."New value: +"[URL path segment] Required. The resource name of the contact group to get."

addedInput schema / properties / resourceName / pattern
```
Added value: +"^contactGroups/[^/]+$"
```

changedOutput schema / (root)

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

First observedOct 26, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description does disclose that this is an HTTP GET, that the resource must be owned by the authenticated user, and that the result is returned as JSON. However, it spends more text on request-body construction (typed params vs. `params` map vs. `body_file`) that is irrelevant for a bodyless GET, and says nothing about permission failures or the fact that members are omitted by default (maxMembers defaults to 0).

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 first and last sentences earn their place, but the middle sentence about request bodies, typed-parameter precedence, and `body_file` is generic boilerplate that does not apply to a GET and pushes the sibling routing information to the end.

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 and parameter coverage is complete, so the core purpose is covered. Still, for a tool with no annotations and a non-obvious default (zero members returned unless maxMembers is set), the description should have flagged that behavior rather than generic body-building mechanics.

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 parameter semantics are fully carried by the schema; the description only restates that a contact group resource name is required. Baseline 3 applies since the description adds no format or usage detail beyond the 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 opening sentence gives a precise verb+resource+scope ('Get a specific contact group owned by the authenticated user by specifying a contact group resource name'), and the closing sentence enumerates the sibling operations on the same resource (batchGet, create, delete, list, update), so an agent can identify this as the single-resource read.

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?

Naming the siblings is a useful routing signal, but the description never states the conditions that select this tool over batchGet (multiple groups) or list (discovery). The when-to-use is only implied by the word 'specific'.

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

Deploy Server