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

Manage Contact

manage_contact

Destructive

Create, update, or delete Google contacts with a single call. Manage contact details like emails, phones, addresses, and custom fields.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`urls`	No	List of URL dicts {value, type?}. Supported types: homepage, blog, profile, work, ftp, reservations, other, etc.
`email`	No	[DEPRECATED] Email address. Use emails=[{"address":..., "type":"other"}].
`notes`	No	Additional notes (for create/update).
`phone`	No	[DEPRECATED] Single phone number. Use phones=[{"number":..., "type":"mobile"}].
`action`	Yes	The action to perform: "create", "update", or "delete".
`emails`	No	List of email dicts {address, type?}.
`phones`	No	List of phone dicts {number, type?}. Supported types: mobile, work, home, main, workMobile, internal, other, etc. Use type="internal" for internal PBX/ATS short numbers (e.g. 250, 301) — stored as a standalone number without + prefix, displayed as "Internal: 250".
`address`	No	Street address (for create/update).
`birthday`	No	Birthday as 'YYYY-MM-DD', 'MM-DD' (no year), or 'clear'/'' to remove.
`job_title`	No	[DEPRECATED] Job title. Use organizations=[{"title":...}].
`nicknames`	No	List of nickname dicts {value, type?}. Useful for bilingual contacts (e.g. Hebrew/English alternative forms). Android dialer and WhatsApp search both index nicknames, enabling cross-script lookup. Supported types: default, alternate_name, maiden_name, initials, other, etc.
`relations`	No	List of relation dicts {person, type?}. Supported types: spouse, child, parent, friend, manager, assistant, etc.
`urls_mode`	No	How to update urls on "update": "merge" (default), "replace", or "remove". merge dedups by normalized URL (lowercased, trailing slash stripped).	merge
`contact_id`	No	The contact ID. Required for "update" and "delete" actions.
`given_name`	No	First name (for create/update).
`emails_mode`	No	How to update emails on "update": "merge" (default), "replace", or "remove".	merge
`family_name`	No	Last name (for create/update).
`phones_mode`	No	How to update phones on "update": "merge" (default), "replace", or "remove". merge = read-modify-write with dedup by canonicalForm/normalized value. replace = overwrite all phones with provided list. remove = delete phones matching provided numbers.	merge
`organization`	No	[DEPRECATED] Company name. Use organizations=[{"name":...}].
`user_defined`	No	List of custom field dicts {key, value}. Useful for structured data like account numbers, IDs, or custom dates.
`organizations`	No	List of org dicts {name?, title?, department?, jobDescription?, type?}.
`nicknames_mode`	No	How to update nicknames on "update": "merge" (default), "replace", or "remove".	merge
`relations_mode`	No	How to update relations on "update": "merge" (default), "replace", or "remove".	merge
`user_defined_mode`	No	How to update custom fields on "update": "merge" (default), "replace", or "remove". merge overrides value on matching key; new keys appended.	merge
`user_google_email`	Yes	The user's Google email address. Required.
`organizations_mode`	No	How to update orgs on "update": "merge" (default), "replace", or "remove".	merge

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed41 schema fields changedv1.28.0Sep 24, 2026

removedInput schema / properties / address / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / address / type
```
Added value: +"string"
```

removedInput schema / properties / birthday / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / birthday / type
```
Added value: +"string"
```

removedInput schema / properties / contact_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / contact_id / type
```
Added value: +"string"
```

removedInput schema / properties / email / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / email / type
```
Added value: +"string"
```

removedInput schema / properties / emails / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "description": "Typed input for an email entry.",
-      "properties": {
-        "address": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Email address value."
-        },
-        "type": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Email type such as work, home, or other."
-        },
-        "value": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Backward-compatible alias for the email address value."
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / emails / items

Added value: +{
+  "additionalProperties": false,
+  "description": "Typed input for an email entry.",
+  "properties": {
+    "address": {
+      "default": null,
+      "description": "Email address value.",
+      "type": "string"
+    },
+    "type": {
+      "default": null,
+      "description": "Email type such as work, home, or other.",
+      "type": "string"
+    },
+    "value": {
+      "default": null,
+      "description": "Backward-compatible alias for the email address value.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / emails / type
```
Added value: +"array"
```

removedInput schema / properties / family_name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / family_name / type
```
Added value: +"string"
```

removedInput schema / properties / given_name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / given_name / type
```
Added value: +"string"
```

removedInput schema / properties / job_title / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / job_title / type
```
Added value: +"string"
```

removedInput schema / properties / nicknames / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "description": "Typed input for a nickname entry.",
-      "properties": {
-        "type": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Nickname type such as default, alternate_name, maiden_name, initials, or other."
-        },
-        "value": {
-          "description": "Nickname value. Used for bilingual contacts (e.g. Hebrew alternative form).",
-          "type": "string"
-        }
-      },
-      "required": [
-        "value"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / nicknames / items

Added value: +{
+  "additionalProperties": false,
+  "description": "Typed input for a nickname entry.",
+  "properties": {
+    "type": {
+      "default": null,
+      "description": "Nickname type such as default, alternate_name, maiden_name, initials, or other.",
+      "type": "string"
+    },
+    "value": {
+      "description": "Nickname value. Used for bilingual contacts (e.g. Hebrew alternative form).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "value"
+  ],
+  "type": "object"
+}

addedInput schema / properties / nicknames / type
```
Added value: +"array"
```

removedInput schema / properties / notes / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / notes / type
```
Added value: +"string"
```

removedInput schema / properties / organization / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / organization / type
```
Added value: +"string"
```

removedInput schema / properties / organizations / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "description": "Typed input for an organization entry.",
-      "properties": {
-        "department": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Department name."
-        },
-        "jobDescription": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Optional organization job description."
-        },
-        "name": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Organization name."
-        },
-        "title": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Job title."
-        },
-        "type": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Organization type such as work or school."
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / organizations / items

Added value: +{
+  "additionalProperties": false,
+  "description": "Typed input for an organization entry.",
+  "properties": {
+    "department": {
+      "default": null,
+      "description": "Department name.",
+      "type": "string"
+    },
+    "jobDescription": {
+      "default": null,
+      "description": "Optional organization job description.",
+      "type": "string"
+    },
+    "name": {
+      "default": null,
+      "description": "Organization name.",
+      "type": "string"
+    },
+    "title": {
+      "default": null,
+      "description": "Job title.",
+      "type": "string"
+    },
+    "type": {
+      "default": null,
+      "description": "Organization type such as work or school.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / organizations / type
```
Added value: +"array"
```

removedInput schema / properties / phone / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / phone / type
```
Added value: +"string"
```

removedInput schema / properties / phones / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "description": "Typed input for a phone entry.",
-      "properties": {
-        "number": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Phone number value."
-        },
-        "type": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Phone type such as mobile, work, home, or internal."
-        },
-        "value": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Backward-compatible alias for the phone number value."
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / phones / items

Added value: +{
+  "additionalProperties": false,
+  "description": "Typed input for a phone entry.",
+  "properties": {
+    "number": {
+      "default": null,
+      "description": "Phone number value.",
+      "type": "string"
+    },
+    "type": {
+      "default": null,
+      "description": "Phone type such as mobile, work, home, or internal.",
+      "type": "string"
+    },
+    "value": {
+      "default": null,
+      "description": "Backward-compatible alias for the phone number value.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / phones / type
```
Added value: +"array"
```

removedInput schema / properties / relations / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "description": "Typed input for a relation entry (spouse, parent, child, etc.).",
-      "properties": {
-        "person": {
-          "description": "The related person's name (matched against contact names by Google Assistant).",
-          "type": "string"
-        },
-        "type": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "Relation type: spouse, child, parent, father, mother, sister, brother, friend, manager, assistant, partner, sibling, domesticPartner, or custom."
-        }
-      },
-      "required": [
-        "person"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / relations / items

Added value: +{
+  "additionalProperties": false,
+  "description": "Typed input for a relation entry (spouse, parent, child, etc.).",
+  "properties": {
+    "person": {
+      "description": "The related person's name (matched against contact names by Google Assistant).",
+      "type": "string"
+    },
+    "type": {
+      "default": null,
+      "description": "Relation type: spouse, child, parent, father, mother, sister, brother, friend, manager, assistant, partner, sibling, domesticPartner, or custom.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "person"
+  ],
+  "type": "object"
+}

addedInput schema / properties / relations / type
```
Added value: +"array"
```

removedInput schema / properties / urls / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "description": "Typed input for a URL entry.",
-      "properties": {
-        "type": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "default": null,
-          "description": "URL type such as homepage, blog, profile, work, ftp, reservations, or other. Custom values allowed."
-        },
-        "value": {
-          "description": "The URL value (e.g. https://example.com).",
-          "type": "string"
-        }
-      },
-      "required": [
-        "value"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / urls / items

Added value: +{
+  "additionalProperties": false,
+  "description": "Typed input for a URL entry.",
+  "properties": {
+    "type": {
+      "default": null,
+      "description": "URL type such as homepage, blog, profile, work, ftp, reservations, or other. Custom values allowed.",
+      "type": "string"
+    },
+    "value": {
+      "description": "The URL value (e.g. https://example.com).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "value"
+  ],
+  "type": "object"
+}

addedInput schema / properties / urls / type
```
Added value: +"array"
```

removedInput schema / properties / user_defined / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "description": "Typed input for a userDefined custom field entry.",
-      "properties": {
-        "key": {
-          "description": "Custom field key (e.g. 'ID', 'Hebrew Birthday', 'Account Number').",
-          "type": "string"
-        },
-        "value": {
-          "default": "",
-          "description": "Custom field value. May be omitted when using remove mode (only the key is needed).",
-          "type": "string"
-        }
-      },
-      "required": [
-        "key"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / user_defined / items

Added value: +{
+  "additionalProperties": false,
+  "description": "Typed input for a userDefined custom field entry.",
+  "properties": {
+    "key": {
+      "description": "Custom field key (e.g. 'ID', 'Hebrew Birthday', 'Account Number').",
+      "type": "string"
+    },
+    "value": {
+      "default": "",
+      "description": "Custom field value. May be omitted when using remove mode (only the key is needed).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "key"
+  ],
+  "type": "object"
+}

addedInput schema / properties / user_defined / type
```
Added value: +"array"
```

Addedv1.0.1Jul 31, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already communicate destructiveHint=true, idempotentHint=false, and readOnlyHint=false, and the description does not contradict them. It adds action-level semantics (create/update/delete) but does not describe side effects, required permissions, or irreversibility beyond what the annotations already signal.

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 two short sentences, front-loaded with the core action and followed by useful consolidation context. There is no filler, repetition, or unnecessary detail.

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?

For a 26-parameter CRUD tool, the description is appropriately high-level, while the 100% schema coverage, rich per-field descriptions, annotations, and output schema cover the invocation details. It does not explicitly highlight that update/delete require contact_id, but the schema states that clearly.

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%, and every parameter has a schema-level description, so the description adds no parameter-level meaning. The baseline of 3 applies because the schema carries the full explanatory burden.

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 names three specific actions (create, update, delete) and a clear resource (contact), and explicitly frames the tool as the consolidated replacement for create_contact, update_contact, and delete_contact. This makes its role unambiguous and distinguishes it from read-only contact tools.

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?

It clearly states that this tool consolidates the three action-specific tools, so an agent knows to route contact CRUD requests here. It does not explicitly discuss alternatives like list_contacts, get_contact, search_contacts, or manage_contacts_batch, but those are not alternatives for the same mutation purpose.

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

Deploy Server