Skip to main content
Glama

Manage Contact

manage_contact
Destructive

Create, update, or delete contacts in Google Contacts. Supports fields like names, phones, emails, organizations, and custom data.

Instructions

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

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The annotations already declare destructiveHint=true, so the description adds no new behavioral insights. It does not detail update modes (merge/replace/remove) or deprecations, which are left to the schema. No contradiction with 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 two sentences, front-loaded with the core purpose and the consolidation key point, with no unnecessary words.

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?

Given the tool's complexity (26 parameters, multiple update modes, deprecated fields), the description is too terse. It doesn't explain the required user_google_email, the action enum, or the merge/replace/remove modes, relying entirely on the schema. For an agent to quickly grasp capabilities, more context is needed.

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 fully documents all 26 parameters, including enums, deprecated fields, and update modes. The tool description adds only the consolidation context, which does not significantly enhance parameter understanding.

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 creates, updates, or deletes a contact and explicitly says it replaces three separate tools (create_contact, update_contact, delete_contact), providing strong differentiation from similar tools like manage_contact_group or get_contact.

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 tells the agent to use this consolidated tool instead of the three individual ones, giving clear context on when to use it. However, it doesn't mention alternatives like manage_contacts_batch for batch operations, nor does it specify when not to use it.

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

Install Server

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/theolefort-cyber/mcpworkspace'

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