Well

Add contact channel

well_add_contact_channel

Add a contact channel to a company or person.

Wraps the resource-scoped REST endpoints (POST /v1/{companies,people}/:id/{emails,phones,web-links,locations}).

channel + the matching value field:

email → value.email
phone → value.e164_number (E.164; a leading "+" is added if missing)
web_link → value.url (+ optional value.platform, default "website")
location → value.city, value.country (+ optional address_line1/2, region, postal_code) value.label is optional (defaults to "work").

NOTE: adding a phone is supported on a PERSON but NOT on a company (no endpoint) — that combination returns a clear error. To READ existing channels, use well_query_records on the parent (companies/people) or the channel root.

Input Schema

TableJSON Schema

Name	Required	Description
`value`	Yes	Channel value — fill the field(s) for the chosen channel
`parent`	Yes	Parent record type: company or person
`channel`	Yes	Channel to add: email \| phone \| web_link \| location
`parent_id`	Yes	UUID of the parent company or person
`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.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`parent`	No
`channel`	No
`success`	Yes
`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.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 22, 2026

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "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.",
+  "type": "string"
+}

addedOutput schema / properties / conversation_id

Added value: +{
+  "description": "The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.",
+  "type": "string"
+}

addedOutput schema / properties / conversation_id_note

Added value: +{
+  "description": "Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.",
+  "type": "string"
+}

addedOutput schema / properties / conversation_id_source

Added value: +{
+  "description": "Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.",
+  "enum": [
+    "host_meta",
+    "argument",
+    "minted"
+  ],
+  "type": "string"
+}

Changed9 schema fields changedSep 17, 2026
- addedInput schema / properties / value / properties / address_line1 / maxLength
```
Added value: +255
```
- addedInput schema / properties / value / properties / address_line2 / maxLength
```
Added value: +255
```
- addedInput schema / properties / value / properties / city / maxLength
```
Added value: +255
```
- addedInput schema / properties / value / properties / country / maxLength
```
Added value: +2
```
- addedInput schema / properties / value / properties / e164_number / maxLength
```
Added value: +255
```
- addedInput schema / properties / value / properties / email / maxLength
```
Added value: +320
```
- addedInput schema / properties / value / properties / postal_code / maxLength
```
Added value: +255
```
- addedInput schema / properties / value / properties / region / maxLength
```
Added value: +255
```
- addedInput schema / properties / value / properties / url / maxLength
```
Added value: +255
```

Changed1 schema field changedAug 31, 2026

changedInput schema / properties / workspace_id / description

Previous value: -"Target workspace. Omit to use the only authorized workspace, or (for read tools) to query all authorized workspaces grouped by workspace. Required for write tools when the token authorizes more than one workspace."New value: +"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."

First observedJul 27, 2026

TDQS

A5/5.0

Behavior5/5

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

Goes beyond annotations by disclosing POST semantics, phone normalization (leading '+' added), defaults (label 'work', platform 'website'), and the error case for unsupported phone on company. No contradiction with readOnlyHint=false or destructiveHint=false.

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?

Front-loaded purpose, then endpoint, then a compact mapping list, and a note with edge cases. Each line adds value, no filler, well organized for scanning.

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?

Given 100% schema coverage, an output schema, and annotations already covering read-only/destructive hints, the description covers the essential usage rules, per-channel fields, defaults, and a key exclusion. Generic auth/rate-limit details are not needed here.

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

Parameters5/5

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

The channel-to-field mapping (email→email, phone→e164_number, web_link→url, location→city/country) is essential for correct invocation and goes well beyond the generic schema descriptions. It also clarifies optional fields and defaults.

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

Purpose5/5

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

States a specific verb and resource: 'Add a contact channel to a company or person.' The REST endpoint reference and channel-type enumeration further distinguish it from read/remove siblings like well_query_records and well_remove_contact_channel.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly notes when not to use (phone on company) and provides an alternative for reading (well_query_records). This gives clear when/how vs. when-not guidance beyond the title.

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

All Well tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?