Skip to main content
Glama

google-contacts_update_contact

Update an existing Google Contact by specifying fields to change and including the etag from the current contact state to prevent update conflicts.

Instructions

Update an existing contact. IMPORTANT: Include the 'etag' field in the request body to prevent conflicts. Get the current etag by first calling get_contact or from a previous create/update response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
etagYesETag from the contact's current state (obtained from get_contact, create_contact, or previous update_contact response). Required for concurrency control and conflict prevention.
urlsNoArray of URL objects to update
namesNoArray of name objects to update
sourcesNoSources to update the contact in
addressesNoArray of address objects to update
birthdaysNoArray of birthday objects to update
biographiesNoArray of biography objects to update
personFieldsNoComma-separated list of fields to return in response
phoneNumbersNoArray of phone number objects to update
organizationsNoArray of organization objects to update
emailAddressesNoArray of email address objects to update
updatePersonFieldsYesComma-separated list of fields to update (e.g., 'names,emailAddresses,phoneNumbers')
person.resourceNameYesResource name of the contact (e.g., 'people/c1234567890')
Behavior3/5

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

No annotations are provided, so the description carries full burden. It highlights the etag requirement for concurrency control, but does not disclose other behavioral traits such as whether updating replaces or merges fields, what happens on error, or the nature of partial updates via updatePersonFields.

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?

Two sentences efficiently convey purpose and critical usage detail. The description is front-loaded with the main action and immediately follows with an essential caution, with no redundant or irrelevant content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 13 parameters, full schema coverage, and no output schema, the description is complete enough for typical use but could add details about return behavior or side effects. The concurrency guidance is valuable, but some behavioral context is missing.

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 coverage, the schema already documents each parameter. The description adds value by emphasizing the importance of the etag parameter and how to obtain it, but does not provide additional clarity beyond what the schema descriptions offer for other parameters.

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 'Update an existing contact' clearly states the verb and resource. It distinguishes from sibling tools like create_contact, delete_contact, and get_contact, which have different purposes.

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 provides explicit guidance to include the etag field and retrieve it from get_contact or previous responses, helping to prevent conflicts. However, it does not explicitly state when not to use this tool or list alternatives beyond the implied prerequisite of getting the contact first.

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/w-10-m/gsuite'

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