grr

Overview Schema Source Related Servers Discussions Admin

people.contactGroups.create

Creates a new contact group for the authenticated user; use it to add a uniquely named group, since duplicate names return HTTP 409.

Instructions

Create a new contact group owned by the authenticated user. Created contact group names must be unique to the users contact groups. Attempting to create a group with a duplicate name will return a HTTP 409 error. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures [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 CreateContactGroupRequest object accepting contactGroup, readGroupFields; pass it via params or whole via body_file Siblings over the same resource: batchGet, delete, get, 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. The body is a JSON CreateContactGroupRequest object.
`request_body`	No	Request body of type CreateContactGroupRequest: pass it via `params` (merged into the built body) or whole via `body_file`.

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.

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 CreateContactGroupRequest object."

addedInput schema / properties / request_body

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

Changed1 schema field changedOct 26, 2026

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

A4.1/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 burden and does well: it discloses the duplicate-name failure mode and its status code, the serialization requirement for concurrent mutations, that the call is refused under --readonly profiles, and that the API response resource is returned as JSON. It stops short of stating auth scopes or that the created group appears in list results afterward.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the uniqueness constraint, then transitions to mechanics and siblings — a sensible order. The '— creates or triggers a change; refused under --readonly safety profiles' clause is boilerplate that adds bulk but does convey a real behavioral limit, so it earns its 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?

With an output schema present, return values needn't be explained, and the description covers the request body type, error behavior, and concurrency caveat. The remaining gap is permission/scope requirements for creating a group on the authenticated user's account, which would close the loop for a mutation tool with zero annotation coverage.

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 parameter and request-body fields are already documented structurally. The description adds that the body accepts contactGroup and readGroupFields and how to supply it (params vs body_file), which is useful but largely restates the schema's own body_file and params descriptions; baseline 3 is warranted rather than more.

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 (create), resource (contact group), and ownership scope (owned by the authenticated user) in the first sentence, and enumerates the sibling operations on the same resource so the agent can place it precisely among list/get/update/delete/batchGet.

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 concrete usage constraints: names must be unique and duplicates yield HTTP 409, and mutate requests for the same user must be serialized. It names siblings but does not explicitly say when to prefer update over create (e.g., to add members after creation), so routing guidance is strong but not complete.

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

Deploy Server