GAM MCP Server

gam_admin_sync_group_members

Synchronize a Google Group's membership to match a target list, adding or removing members concurrently.

Instructions

Synchronizes a Google Group's membership against a target list, adding/removing concurrently.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "adminUserEmail": "<adminUserEmail>",
      "groupEmail": "<groupEmail>",
      "targetMembers": "<targetMembers>"
    },
    "name": "gam_admin_sync_group_members"
  }
}

Input Schema

Name	Required	Description
`dryRun`	No	Compute diffs without writing (default true).
`groupEmail`	Yes	The target Google Group email address.
`targetMembers`	Yes	The complete desired list of member emails.
`adminUserEmail`	Yes	The administrator email to impersonate.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 8, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description discloses key behavior (add/remove concurrently) but lacks detail on idempotency, failure modes, permissions, and the dryRun parameter (which is critical for safety). No annotations exist to supplement, so the description carries the burden and falls short.

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?

The description is extremely concise (one sentence, 11 words) and front-loaded. It immediately communicates the tool's purpose without any fluff.

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?

Given no output schema, the description does not explain what the tool returns or error behavior. It covers the main function but is incomplete for a sync tool that likely produces diffs or status messages. The dryRun parameter's output is not mentioned.

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 coverage is 100%, so parameters are described in the schema. The description adds no additional parameter context beyond the schema. It does not explain how targetMembers relates to existing membership or the role of adminUserEmail.

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 clearly states the verb 'synchronizes', the resource 'Google Group's membership', and the method 'adding/removing concurrently'. It differentiates from sibling tools like gam_admin_print_group_members (read-only) and gam_admin_create_user (user creation).

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 lacks explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, idempotency, or cautionary notes. Usage is implied as a bulk sync operation but 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