google-workspace-mcp

contacts_list_groups

List all contact groups from your Google Contacts account. Use this to view and manage labels that organize your contacts.

Instructions

List all contact groups (labels).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "contacts_list_groups"
  }
}

Input Schema

Name	Required	Description	Default
`max_results`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'List all contact groups (labels)' and provides no details about pagination, the max_results parameter, whether the list is ordered, or any side effects. While 'list' implies a read operation, the description lacks substantive behavioral context.

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 a single, concise sentence that immediately conveys the core action and resource. There is no redundant information, and the structure is clear and efficient for a simple utility.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While an output schema exists and the tool is relatively simple, the description omits critical contextual information such as how max_results behaves, whether all groups are returned, or how this relates to other group-management tools. This leaves gaps for an agent deciding on invocation and interpreting results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema includes a max_results parameter with a default of 50, but the description does not explain its meaning, acceptable values, or effect on results. Since schema description coverage is 0%, the description should compensate, but it does not mention any parameter details.

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 tool's action ('List') and resource ('all contact groups'), and even clarifies that groups are also called 'labels'. It is distinct from sibling tools like contacts_list and contacts_search, which operate on individual contacts rather than groups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no mention of related tools like contacts_create_group or contacts_modify_group_members, nor any context about typical use cases such as retrieving a group overview before assigning contacts.

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

Deploy Server