icloud-mcp

Overview Schema Source Related Servers Discussions Admin

Contacts Update

contacts_update

Destructive

Update an iCloud contact's name, title, organization, notes, emails, phones, or addresses. Only provided fields change; list fields replace existing values.

Instructions

Update a contact. Only provided fields change; list fields replace the existing values (entries that keep the same number/address keep their labels such as home/work).

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New full name.
`notes`	No	New notes (empty string clears).
`title`	No	New job title.
`emails`	No	New email list (replaces existing).
`phones`	No	New phone list (replaces existing).
`addresses`	No	New address list (replaces existing).
`contact_id`	Yes	Contact URL/ID from contacts_list or contacts_search.
`organization`	No	New organization.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 27, 2026

TDQS

A4/5.0

Behavior5/5

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

Description reveals key behaviors: only provided fields are modified, list fields replace existing values, and matching entries preserve labels. These details go beyond the annotations (destructiveHint=true) and clarify the partial-update semantics.

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 concise sentences immediately deliver the core action and the most important behavioral caveat. No filler.

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 update tool with a full schema, output schema, and annotations, the description covers the essential behavioral semantics. It doesn't need to enumerate parameters; the schema handles that.

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 parameters are documented. Description adds important semantics that only provided fields change and list replacement behavior, which supplements the schema's per-field descriptions.

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 ('Update') and resource ('a contact'), and clarifies that only provided fields change. Does not explicitly name sibling tools for differentiation, but the purpose is unambiguous.

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?

No explicit guidance on when to use this tool versus alternatives such as contacts_create or contacts_delete. It is implied by the name and sibling set, but there is no condition or exclusion stated.

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