Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Manage Contact Group

manage_contact_group

Destructive

Manage Google contact groups by creating, updating, deleting groups, and adding or removing members.

Instructions

Create, update, delete a contact group, or modify its members. Consolidated tool replacing create_contact_group, update_contact_group, delete_contact_group, and modify_contact_group_members.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	The group name. Required for "create" and "update" actions.
`action`	Yes	The action to perform: "create", "update", "delete", or "modify_members".
`group_id`	No	The contact group ID. Required for "update", "delete", and "modify_members" actions.
`add_contact_ids`	No	Contact IDs to add (for "modify_members").
`delete_contacts`	No	If True and action is "delete", also delete contacts in the group (default: False).
`user_google_email`	Yes	The user's Google email address. Required.
`remove_contact_ids`	No	Contact IDs to remove (for "modify_members").

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv1.28.0Sep 24, 2026

removedInput schema / properties / add_contact_ids / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / add_contact_ids / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / add_contact_ids / type
```
Added value: +"array"
```

removedInput schema / properties / group_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / group_id / type
```
Added value: +"string"
```

removedInput schema / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / name / type
```
Added value: +"string"
```

removedInput schema / properties / remove_contact_ids / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / remove_contact_ids / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / remove_contact_ids / type
```
Added value: +"array"
```

Addedv1.0.1Jul 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating tool. The description adds value by enumerating the four distinct operations (create, update, delete, modify_members) and noting the delete_contacts parameter behavior. It doesn't contradict annotations and provides useful context about the consolidated nature of the tool.

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

Conciseness5/5

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

Two sentences with zero waste. The first sentence states the full scope of operations, and the second sentence names the legacy tools it replaces. Every word 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?

The description is complete for a consolidated CRUD tool: it lists all operations, names the replaced tools, and the schema covers all parameters with 100% coverage. The output schema exists, so return values are documented elsewhere. Minor gap: it doesn't mention prerequisites like needing an existing group for update/delete, but the schema's required fields partially cover this.

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 schema already documents all 7 parameters thoroughly. The description adds a high-level summary of what the tool does but doesn't add parameter-level detail beyond the schema. Baseline 3 is appropriate since the schema carries the heavy lifting.

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 description states a specific verb and resource: 'Create, update, delete a contact group, or modify its members.' It also explicitly names the four legacy tools it replaces, which distinguishes it from siblings like manage_contact and list_contact_groups. This is a clear, consolidated tool definition.

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?

The description explains that this is a consolidated tool replacing four specific tools, which tells the agent when to use it instead of those alternatives. However, it doesn't explicitly state when not to use it or mention alternatives like manage_contact for individual contact operations. The context is clear but exclusions are not exhaustive.

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

Deploy Server