Update person
well_update_personUpdate an existing person (contact) in the current workspace.
Use this tool when the user asks to change, fix, rename, or edit a person's fields.
REQUIRED: person_id OPTIONAL (only include fields the user wants changed): first_name, last_name, job_title, timezone, locale, birthdate (MM-DD or YYYY-MM-DD; year 0004 means the year is unknown), tags, remove_tags, hidden.
For a new person, use well_create_person first, then call this tool with the returned person_id to save their birthday. Pass birthdate as null to clear the date.
TAGS: tags adds workspace tags to the person and keeps the tags they already carry. remove_tags takes tags off the person, by name; the workspace tag itself stays. To change a status kept as a tag, send both in one call: the new tag in tags and the old one in remove_tags. One name in both lists is refused.
HIDE: hidden: true hides the person from Well's lists and figures and keeps the row; hidden: false shows them again. It works on a person a connected tool synced in too, since no sync writes it. When the person asks to delete a synced contact, well_delete_person refuses and offers this hide: ask, then call this tool with only person_id and hidden: true.
NOT CHANGEABLE via this tool: emails, phones, locations, linked companies, media. Those require dedicated tools (not yet available).
Returns { success: true, person_id, full_name } on success, with tags (the person's tags after the change) when the call sent tags or remove_tags, or { success: false, error } on failure. In Well's own chat, a call that saves a birthday also returns birthday: { date, reminders }: the next date of the birthday and the days Well reminds the member of it, all YYYY-MM-DD. Read the reminder days back from it; never compute them. An MCP call does not return this field.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Tags to add to this person; the tags the person already carries stay | |
| hidden | No | true hides the row from Well's lists and figures and keeps it, with every value a connected tool wrote; false shows it again. Omit to leave it as it is. | |
| locale | No | Person's language; pass null to clear | |
| timezone | No | Person's time zone; pass null to clear | |
| birthdate | No | Birthday as MM-DD or YYYY-MM-DD; year 0004 means the year is unknown | |
| job_title | No | Job title; pass null to clear | |
| last_name | No | Last name | |
| person_id | Yes | The UUID of the person to update (required) | |
| first_name | No | First name | |
| remove_tags | No | Tags to take off this person, by name; the workspace tag itself stays | |
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| idempotency_key | No | Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | ||
| tags | No | ||
| error | No | ||
| success | Yes | ||
| birthday | No | ||
| previous | No | ||
| full_name | No | ||
| person_id | No | ||
| reply_lines | No | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| near_candidates | No | ||
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. | |
| near_candidates_truncated | No |