Niches · Contacts & address books
Add or update a contact without making a duplicate
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
Before creating, the agent can find an existing record by email or phone; create and update accept every field the docs list (phones, addresses, organisation, custom fields), updates use an etag or version so a stale write is refused with a clear error, and the docs say how duplicates are merged or flagged for review.
How agents ask for it: save this person's details
, update Jo's new number
, add the people from this email thread
Does the job, with a limit 3
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| ContactsPlus E Contacts Plus LLC | Search before create; contacts.update takes the current etag and a resolveConflicts flag. No idempotency key, the stale-etag error is not documented, and dedupe is an app feature; MCP writes land in Suggestions for the owner to approve. source |
| Google People API B Google LLC | Search first, then createContact; updates need the source etag and a stale one returns 400 failedPrecondition. No idempotency key on create, mutations for a user must be sequential, acc-07 saw etag mismatches on fresh etags, and acc-08 lost fields on create. source |
| Microsoft Graph People and Contacts API C Microsoft Corporation | Look up first with $filter on emailAddresses/any, then create or PATCH with Contacts.ReadWrite. No idempotency key, no etag or If-Match precondition is documented on update (only changeKey in the body), and no duplicate merge is described. source |
What stops agents finishing
- no idempotency key on create, so a retry duplicates
- write not visible to search for minutes
- etag mismatch on back-to-back updates
Around it
Before: mailbox-access.read-thread, document-extraction.read-card. After: contacts.sync-copy, crm.upsert-contact.
Where this comes from
Weight 24 of 100 in Contacts & address books: 5 accounts (acc-07 to acc-11) on etag errors, missing fields and duplicates
The same as data: /api/v1/use-cases/contacts.save-contact.json, or the MCP tool get_use_case with id contacts.save-contact. Other jobs in this category: /api/v1/niches?category=contacts.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.