Skip to main content
Glama
iTvX

Google Workspace MCP — Gmail edition

by iTvX

manage_contacts

Search, read, create, update, and delete Google Contacts, including saved contacts, past correspondents, and your organization's directory.

Instructions

Search, read, create, update and delete Google Contacts: your saved contacts, the addresses you have corresponded with but never saved, and your organization's directory.

Input Schema

NameRequiredDescriptionDefault
nameNoFull name, e.g. `Ada Lovelace`. Split into given and family name on the way in; a single word becomes the given name.
emailYesAccount email address. On list operations, "all" runs it once for every configured account.
notesNoFree-text note stored on the contact
phoneNoPhone number, in whatever form you have it — Google normalizes it. On `update` this REPLACES every number the contact has — pass an empty string to clear them.
queryNoText to match against names, email addresses, nicknames and phone numbers. Matching is by PREFIX: `ann` finds Anna, `nna` finds nobody.
companyNoOrganization name
jobTitleNoJob title within the organization
contactIdNoPerson id as `list` or `search` printed it (e.g. `people/c1234567890`). A bare id without the `people/` prefix is accepted.
operationYeslist: list your saved contacts | search: search your saved contacts by name, email, nickname or phone | get: get one person in full — addresses, birthday, notes, relations | create: create a new contact | update: change an existing contact (only the fields you pass; pass an empty string to clear one) | delete: delete a contact | listOther: list 'other contacts' — addresses you have corresponded with but never saved | searchOther: search 'other contacts' by name or email | listDirectory: list people in your organization's directory (Workspace accounts only) | searchDirectory: search your organization's directory by name or email (Workspace accounts only)
pageTokenNoContinue from where a previous page stopped — pass the token that response printed
sortOrderNoOrder for `list` — by first name, by last name, or most recently changed first
maxResultsNoMax people to return (default 25). Capped per operation: 30 for `search` and `searchOther`, 100 for everything else.
contactEmailNoThe contact's email address. (`email` is the account making the call, not the person being saved.) On `update` this REPLACES every address the contact has — pass an empty string to clear them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.8.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it is a single sentence that discloses almost nothing beyond the surface: no mention that delete is irreversible, that update overwrites fields, that directory access requires a Workspace account, or any pagination/rate-limit behavior. The rich destructive semantics (e.g. phone/contactEmail REPLACING all values) live only in the schema, not the description.

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?

One front-loaded sentence with no filler, and the verb set and resource come first. It is efficient, though for a 10-operation, 13-parameter tool the brevity borders on under-specification rather than true conciseness.

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?

For a high-complexity tool — 10 operations, 13 parameters, no annotations, no output schema — the description is not complete enough. It omits the destructive nature of delete, the overwrite semantics of update, account scoping for the email parameter, and the Workspace-only gating of directory operations, leaving the agent to reconstruct behavior from the schema alone.

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 the schema already documents all 13 parameters with unusual thoroughness — including prefix-matching semantics for query, the people/ id format, and the replace-vs-clear behavior of phone and contactEmail. The description adds no parameter meaning of its own, which is the correct baseline when the schema does all the work.

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 names a specific resource (Google Contacts) and enumerates the verb set (search, read, create, update, delete), which cleanly separates it from siblings like manage_calendar or manage_email. It also partitions the resource into three domains — saved contacts, 'other' contacts, and the org directory — that map onto the operation enum. It stops short of naming the individual operations, but the resource is unambiguous.

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?

Usage is implied through the three-domain breakdown (saved vs corresponded-but-unsaved vs directory), which is the actual routing decision between list/search, listOther/searchOther, and listDirectory/searchDirectory. However, the description never states when to prefer this tool over siblings (e.g. contacts lookups while composing email via manage_email), and gives no prerequisites such as the Workspace-only restriction on directory operations.

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