Google Workspace MCP Server

Overview Schema Source Related Servers Discussions Admin

manage_contact

Add, modify, or remove Google contacts by specifying name, email, phone, organization, job title, or notes. Use contact ID for updates or deletions.

Instructions

Create, update, or delete a contact. Consolidated tool replacing create_contact, update_contact, and delete_contact.

Args: user_google_email (str): The user's Google email address. Required. action (str): The action to perform: "create", "update", or "delete". contact_id (Optional[str]): The contact ID. Required for "update" and "delete" actions. given_name (Optional[str]): First name (for create/update). family_name (Optional[str]): Last name (for create/update). email (Optional[str]): Email address (for create/update). phone (Optional[str]): Phone number (for create/update). organization (Optional[str]): Company/organization name (for create/update). job_title (Optional[str]): Job title (for create/update). notes (Optional[str]): Additional notes (for create/update).

Returns: str: Result of the action performed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`email`	No
`notes`	No
`phone`	No
`action`	Yes
`job_title`	No
`contact_id`	No
`given_name`	No
`family_name`	No
`organization`	No
`user_google_email`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.14.3Sep 6, 2026

TDQS

A4.3/5.0

Behavior3/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. It openly states that the tool creates, updates, or deletes and that it returns a string result, but it does not disclose whether delete is permanent, whether update replaces only provided fields, or what side effects or permissions are involved.

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 front-loaded with the core purpose, then presents parameters and return value in a clean Args/Returns structure. Every line adds useful information; there is no filler or redundancy.

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 ten parameters and no annotations, the description covers all required invocation details, conditional behaviors, and return type. It is slightly light on deeper operational context such as how to obtain a contact_id and how update semantics handle omitted fields, but it is sufficient for calling the tool correctly.

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

Parameters5/5

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

Schema description coverage is 0%, and the description compensates fully by documenting all 10 parameters, including the purpose of each and conditional requirements such as contact_id being required for update and delete. This adds significant meaning beyond the bare schema.

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 opens with 'Create, update, or delete a contact,' which is a specific verb-resource statement, and explicitly says it consolidates create_contact, update_contact, and delete_contact. This clearly distinguishes it from the sibling batch tool manage_contacts_batch.

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

Usage Guidelines4/5

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

The description gives clear usage context by defining the three actions and stating that contact_id is required for update and delete. It does not explicitly mention when not to use this tool in favor of manage_contacts_batch, but the singular 'contact' in the name and the consolidation statement make the intended use clear.

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

Deploy Server