gmail-multi-mcp

Overview Schema Source Related Servers Discussions Admin

List contacts

contacts_list

Read-onlyIdempotent

Page through an account's address book, newest changes first. Use the returned page token to load the next set of contacts.

Instructions

Page through an account address book, most recently changed first. Returns "nextPageToken" when there is more; pass it back as "page_token" for the next page. Use contacts_search when you are looking for someone in particular.

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": {
      "account": "<account>"
    },
    "name": "contacts_list"
  }
}

Input Schema

Name	Required	Description
`account`	Yes	Configured account: the email address, or the alias given at setup.
`page_size`	No	Contacts per page. Default 50, maximum 200.
`page_token`	No	The "nextPageToken" from the previous call. Omit for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false; the description adds behavioral detail beyond that: ordering by most recently changed and the token-based pagination contract. It does not cover rate limits or auth, but those are not essential given the annotations and the account parameter.

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?

Three short sentences, front-loaded with the core behavior, then token mechanics, then the sibling alternative. No filler or redundant clauses.

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

Completeness5/5

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

For a read-only paged list tool, the description plus high-coverage schema and annotations is enough to invoke correctly. It covers ordering, pagination, and the search alternative; the absent output schema is not a blocker because the return shape is not needed to make the call.

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 account, page_size, and page_token are already documented. The description mainly reinforces the page_token round-trip, which is already in the schema, so it adds little parameter meaning beyond the baseline.

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 identifies a specific action (paging through the address book) and resource (account address book), and adds the sort order. It also names contacts_search as the sibling for targeted lookup, so an agent can differentiate the tools without opening schemas.

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

Usage Guidelines5/5

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

It explicitly states when to prefer contacts_search ('looking for someone in particular'), implying contacts_list is for browsing or enumerating contacts. It also frames the pagination workflow, making clear this is the paging tool.

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