Skip to main content
Glama

update_contact

Modify a contact by sending only fields to change; add or remove emails and phones, replace addresses, and get previous values to undo edits.

Instructions

Change a contact. Send only the fields to change. Text fields replace the old value, and an empty string clears them. Emails and phones change with 'add_emails', 'remove_emails', 'add_phones' and 'remove_phones' (remove by value). 'addresses' replaces all addresses, and [] removes them. The result has 'previous' with the old values of the fields you sent, so you can undo the change. Notes are not supported. macOS refuses to change a contact that has a note, unless the app has a special Apple entitlement. Then the tool returns an error and nothing changes.

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": {
      "id": "<id>"
    },
    "name": "update_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesContact id from search_contacts. Use it as given.
birthdayNoNew birthday. Date as 2026-11-12, or --11-12 when the year is not known. Empty string clears it.
addressesNoList of postal addresses. Each has at least one of street, city, state, postal_code, country.
job_titleNoNew job title. Empty string clears it.
add_emailsNoList of {label, value} objects with the email address to add.
add_phonesNoList of {label, value} objects with the phone number to add.
given_nameNoNew first name. Empty string clears it.
family_nameNoNew last name. Empty string clears it.
organizationNoNew organization. Empty string clears it.
remove_emailsNoEmail addresses to remove (ignores case).
remove_phonesNoPhone numbers to remove. Spaces and dashes do not matter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-open-world mutation. The description still adds real behavioral context on top: text fields replace, empty string clears, addresses are replaced wholesale, removed by value for emails/phones, and the response carries 'previous' values enabling undo. The apparent tension between 'addresses ... [] removes them' and destructiveHint=false is resolved by the undo/previous guarantee, so this is disclosure rather than contradiction, though the mutation surface is only partly spelled out.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six dense sentences, each carrying a distinct rule, with the invocation rule front-loaded and the failure mode placed last. No filler, though the notes/entitlement paragraph is wordy relative to its single actionable point.

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

Completeness5/5

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

For an 11-parameter mutation tool with no output schema, the description covers invocation, per-field update semantics, the shape of the result ('previous' values), and a concrete failure mode that leaves the contact unchanged. An agent has enough to call this correctly and to explain a refusal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the per-field meanings are already documented, but the description adds update-mode semantics the schema does not carry: whole-list replacement for addresses, add/remove merges for emails and phones, and replace-vs-clear behavior for text fields. It does not cover 'id' or the label conventions, which the schema handles.

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?

Opens with a specific verb and resource ('Change a contact') and the rest of the text makes clear this is a partial-update operation against an existing contact, which separates it from create_contact, delete_contact and get_contact. It never names a sibling explicitly, so it stops short of full differentiation.

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?

'Send only the fields to change' tells the agent how to invoke it, and the notes/macOS paragraph gives an explicit precondition under which the call fails. What is missing is a direct statement of when to pick this over update_note or other update tools, and there is no guidance on what to do when the note error is hit.

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