Skip to main content
Glama

manage_contact_groups

Idempotent

List or create Google Contacts labels and add or remove contacts from groups to keep contacts organized by category.

Instructions

List, create, or assign/remove contacts from Google Contact labels/groups (contactGroups).

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": {
      "action": "<action>"
    },
    "name": "manage_contact_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoGroup name when action='create'
actionYesOperation to perform on contact groups
addResourceNamesNoContact resourceNames to add to the group
groupResourceNameNoGroup resourceName (e.g. 'contactGroups/12345') when action='modify_members'
removeResourceNamesNoContact resourceNames to remove from the group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=true and openWorld=true, so the description does not need to restate safety. What it should add but does not: that assign/remove only changes group membership (contacts are not deleted), that modify_members requires an existing contactGroups/... identifier, and any auth prerequisite. There is also unresolved tension between the 'create' action and the idempotentHint=true annotation, which the description does nothing to clarify.

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?

A single front-loaded sentence with no filler, and the resource is named first. It is slightly compressed — 'assign/remove contacts from ... labels/groups' takes a moment to parse — but nothing is wasted.

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?

For a 5-parameter, multi-action tool with no output schema, the description covers what the tool does but not what each action returns (list's result shape, or whether modify_members echoes the updated membership). Annotations cover the safety profile, but the return-value gap is unfilled.

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 every parameter including the action enum and the add/remove resourceName arrays is already documented in the schema. The description reinforces the action-to-field mapping but adds no format, ordering, or constraint detail beyond it, so the baseline 3 applies.

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?

States a specific verb set (list, create, assign/remove) against a specific resource (Google Contact groups / contactGroups), and the parenthetical API name makes the resource unambiguous. It distinguishes this from the sibling contact-CRUD tools implicitly by operating on groups rather than contacts, though it never names a sibling explicitly.

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 three actions in the description map directly to the action enum, so the modes of use are implied, but there is no when-to-use guidance, no prerequisite (e.g. authentication, or that a groupResourceName must already exist before modify_members), and no exclusions relative to the sibling contact tools.

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