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

List Contacts

list_contacts

Read-onlyIdempotent

Retrieve and paginate an authenticated user's Google contacts, with sorting and optional full or incremental sync to fetch changed or deleted contacts.

Instructions

List contacts for the authenticated user, optionally as a full or incremental sync.

Input Schema

Name	Required	Description
`page_size`	No	Maximum number of contacts to return (default: 100, max: 1000).
`page_token`	No	Token for pagination. Keep all other arguments unchanged when following it.
`sort_order`	No	Sort order: "LAST_MODIFIED_ASCENDING", "LAST_MODIFIED_DESCENDING", "FIRST_NAME_ASCENDING", or "LAST_NAME_ASCENDING". Not supported when syncing.
`sync_token`	No	List only changes since the sync that returned this token, marking deleted contacts. The last page returns a new sync token.
`user_google_email`	Yes	The user's Google email address. Required.
`request_sync_token`	No	Start a full sync. The last page returns a sync token.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.2.0Oct 24, 2026

changedInput schema / properties / page_token / description

Previous value: -"Token for pagination."New value: +"Token for pagination. Keep all other arguments unchanged when following it."

addedInput schema / properties / request_sync_token

Added value: +{
+  "default": false,
+  "description": "Start a full sync. The last page returns a sync token.",
+  "type": "boolean"
+}

changedInput schema / properties / sort_order / description

Previous value: -"Sort order: \"LAST_MODIFIED_ASCENDING\", \"LAST_MODIFIED_DESCENDING\", \"FIRST_NAME_ASCENDING\", or \"LAST_NAME_ASCENDING\"."New value: +"Sort order: \"LAST_MODIFIED_ASCENDING\", \"LAST_MODIFIED_DESCENDING\", \"FIRST_NAME_ASCENDING\", or \"LAST_NAME_ASCENDING\". Not supported when syncing."

addedInput schema / properties / sync_token

Added value: +{
+  "default": null,
+  "description": "List only changes since the sync that returned this token, marking deleted contacts. The last page returns a new sync token.",
+  "type": "string"
+}

Changed4 schema fields changedv1.28.0Sep 24, 2026
- removedInput schema / properties / page_token / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / page_token / type
```
Added value: +"string"
```
- removedInput schema / properties / sort_order / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / sort_order / type
```
Added value: +"string"
```
Addedv1.0.1Jul 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, open-world operation. The description adds the authenticated-user scope and sync-mode behavior, but does not add further operational context such as pagination expectations or sync semantics beyond what the schema provides.

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 front-loaded sentence with no wasted words. It states the resource, scope, and optional sync capability efficiently.

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?

Given the rich schema, output schema, and annotations, the description is largely complete for correct invocation. The main missing piece is sibling differentiation, especially versus search_contacts and get_contact.

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 all six parameters are already documented in the schema. The description's only extra semantic signal is that full or incremental sync is optional, which is also covered by the sync_token and request_sync_token schema descriptions.

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?

The description states a specific verb and resource: list contacts for the authenticated user. It is clear about scope and sync capability, but it does not distinguish this tool from siblings such as search_contacts or get_contact.

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 phrase 'optionally as a full or incremental sync' implies a sync use case, but the description gives no explicit when-to-use guidance, exclusions, or alternatives such as search_contacts for filtering.

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

Deploy Server