Skip to main content
Glama

Manage Contact

manage_contact
Destructive

Create, update, or delete Google Contacts with complete details—names, emails, phones, addresses, organizations, and custom fields. Manage contact records directly from your assistant.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsNoList of URL dicts {value, type?}. Supported types: homepage, blog, profile, work, ftp, reservations, other, etc.
emailNo[DEPRECATED] Email address. Use emails=[{"address":..., "type":"other"}].
notesNoAdditional notes (for create/update).
phoneNo[DEPRECATED] Single phone number. Use phones=[{"number":..., "type":"mobile"}].
actionYesThe action to perform: "create", "update", or "delete".
emailsNoList of email dicts {address, type?}.
phonesNoList 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".
addressNoStreet address (for create/update).
birthdayNoBirthday as 'YYYY-MM-DD', 'MM-DD' (no year), or 'clear'/'' to remove.
job_titleNo[DEPRECATED] Job title. Use organizations=[{"title":...}].
nicknamesNoList 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.
relationsNoList of relation dicts {person, type?}. Supported types: spouse, child, parent, friend, manager, assistant, etc.
urls_modeNoHow to update urls on "update": "merge" (default), "replace", or "remove". merge dedups by normalized URL (lowercased, trailing slash stripped).merge
contact_idNoThe contact ID. Required for "update" and "delete" actions.
given_nameNoFirst name (for create/update).
emails_modeNoHow to update emails on "update": "merge" (default), "replace", or "remove".merge
family_nameNoLast name (for create/update).
phones_modeNoHow 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
organizationNo[DEPRECATED] Company name. Use organizations=[{"name":...}].
user_definedNoList of custom field dicts {key, value}. Useful for structured data like account numbers, IDs, or custom dates.
organizationsNoList of org dicts {name?, title?, department?, jobDescription?, type?}.
nicknames_modeNoHow to update nicknames on "update": "merge" (default), "replace", or "remove".merge
relations_modeNoHow to update relations on "update": "merge" (default), "replace", or "remove".merge
user_defined_modeNoHow to update custom fields on "update": "merge" (default), "replace", or "remove". merge overrides value on matching key; new keys appended.merge
user_google_emailYesThe user's Google email address. Required.
organizations_modeNoHow to update orgs on "update": "merge" (default), "replace", or "remove".merge

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnly=false, and idempotent=false, and the description's create/update/delete verbs are consistent with those hints. The description adds no deeper behavioral detail such as merge semantics, read-modify-write behavior, or prerequisites for update/delete, but it does not contradict the annotations.

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 filler. The first clause states the core action, and the second clause justifies why this tool exists, earning its place without bloating the definition.

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 very rich input schema, output schema presence, and annotations, the description does not need to enumerate parameters or return behavior. The only minor gap is the lack of an explicit pointer to manage_contacts_batch for multi-contact operations, but the schema and annotations otherwise make the tool sufficiently complete.

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?

With 100% schema description coverage, the schema already documents all 26 parameters in detail, including action-specific requirements and mode semantics. The description itself contributes no additional parameter-level meaning, so it stays at the coverage 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 clearly states the tool's verb-resource scope: 'Create, update, or delete a contact.' It also frames the tool as a consolidated replacement for three legacy tools, making its role in the API unambiguous and easy to distinguish from read-only or batch-oriented 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 Guidelines3/5

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

The description gives useful context by naming the three tools it replaces, which implies this is the single-contact CRUD entry point. However, it does not explicitly address when to use this tool versus sibling manage_contacts_batch or other contact-related tools, leaving the batch-vs-single decision implicit.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WorldCentralKitchen/google_workspace_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server