Skip to main content
Glama

update_contact

Idempotent

Edit an existing Google Contacts entry by resourceName, automatically fetching the latest etag and merging or replacing specified contact fields.

Instructions

Edit an existing contact in Google Contacts by its resourceName (e.g. 'people/c12345'). Fetches the latest etag automatically and merges or replaces the specified fields.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resourceName": "<resourceName>"
    },
    "name": "update_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoWebsite or profile URLs (strings or { value, type })
mergeNoKeep existing fields and merge new emails/phones/notes (default: true)
notesNoBiography or notes about the contact
emailsNoEmail addresses (strings or { value, type: 'work'|'home'|'other' })
phonesNoPhone numbers (strings or { value, type: 'mobile'|'work'|'home'|'other' })
prefixNoHonorific prefix (e.g. Dr., Mr., Ms.)
suffixNoHonorific suffix (e.g. Jr., III, PhD)
birthdayNoBirthday in YYYY-MM-DD or MM-DD format
fullNameNoFull display name (automatically split if givenName/familyName are omitted)
jobTitleNoJob title or role
nicknameNoNickname
addressesNoPhysical addresses (strings or structured address objects)
givenNameNoFirst / given name
photoPathNoOptional local file path to a PNG/JPG photo to set as the contact's avatar
departmentNoDepartment within the organization
familyNameNoLast / family name
middleNameNoMiddle name
photoBase64NoOptional base64-encoded PNG/JPG photo to set as the contact's avatar
customFieldsNoCustom key-value pairs stored on the contact
organizationNoCompany or organization name
resourceNameYesGoogle Contact resourceName (e.g. 'people/c123456789')
groupResourceNamesNoContact group resource names (e.g. ['contactGroups/myContacts'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that the etag is fetched automatically (so the agent needn't handle concurrency tokens) and that the operation either merges or replaces fields. That is real behavioral context. It stops short of describing the response, permission requirements, or what happens to fields not supplied.

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 tight sentences with no filler; the resource identifier and example come first, followed by the two behavioral facts that matter. Nothing is wasted.

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 22-parameter mutation tool with a fully documented schema and no output schema, the description covers the essentials: identification, etag handling, and merge semantics. It could say more about partial updates and photo fields, but nothing critical 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?

Schema coverage is 100%, so all 22 parameters are already documented in the schema. The description reinforces the merge-vs-replace behavior tied to the 'merge' parameter and the resourceName format, but adds little semantic detail beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Edit an existing contact in Google Contacts') and identifies the addressing key (resourceName with an example). The word 'existing' implicitly separates it from create_contact/upsert_contact, but no sibling is named explicitly.

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?

Usage is implied: use this when you already have a resourceName for a contact you want to modify. There is no explicit guidance on when to prefer this over upsert_contact or parse_and_upsert_contact, and no prerequisites or exclusions are stated.

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