Skip to main content
Glama

manage_contact

Create, update, or delete Google contacts. Manage details such as name, phone, email, and organization. Supports merge, replace, or remove modes for phones, emails, and organizations.

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?}.
notesNoAdditional notes (for create/update).
addressNoStreet address (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
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
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
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention side effects (e.g., irreversible changes), required permissions, or rate limits. The schema shows update modes, but the description lacks this context, leaving the agent unaware of nondestructive versus destructive update behaviors.

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 extremely concise with two sentences that front-load the core action and consolidation context. Every sentence earns its place without fluff.

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 has 17 parameters and an output schema, a two-sentence description is inadequate. It omits critical context such as required conditions for update/delete, update modes, and differentiation from batch operations. The description does not sufficiently equip an agent to handle the tool's complexity.

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 coverage is 100%, so the schema itself documents all parameters. The description adds no additional meaning beyond the already detailed schema. A score of 3 is appropriate as the baseline for high coverage.

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 it creates, updates, or deletes a contact and explicitly positions itself as a consolidated replacement for three prior tools. This makes the purpose unambiguous and distinguishes it from other contact-related tools like get_contact or list_contacts.

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

Usage Guidelines2/5

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

The description does not provide any guidance on when to use this tool versus alternatives such as manage_contacts_batch or search_contacts. It only mentions it replaces older tools, which is helpful but insufficient for selecting the right contextual tool.

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/HuntsDesk/ve-gws'

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