Well

Update web link

well_update_web_link

Destructive

Change one web link (a website, LinkedIn, X/Twitter, GitHub or other profile URL) of a company or a person in the current workspace.

Use this tool when the user asks to fix, replace or edit a link the record already has. To add a new link use well_add_contact_channel; to remove one use well_remove_contact_channel.

REQUIRED: parent ("company" or "person"), parent_id, web_link_id (the id of the link row; read it with well_query_records on the parent). OPTIONAL (pass at least one, only what the user wants changed): url, platform. A company link takes twitter, linkedin, github, website or other; a person link also takes instagram and facebook.

The returned web_link_id is the id to use for this link from now on. It can differ from the one you passed: another record held the same link, and that record keeps its own.

Returns { success: true, web_link_id, platform, url } on success, or { success: false, error } on failure.

Input Schema

Name	Required	Description
`url`	No	The new URL. Omit to keep the current one.
`parent`	Yes	The record the link belongs to: company or person
`platform`	No	The new platform. Omit to keep the current one. instagram and facebook are person-only.
`parent_id`	Yes	UUID of the company or person
`web_link_id`	Yes	UUID of the web link row to change
`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
`url`	No
`code`	No
`error`	No
`success`	Yes
`platform`	No
`reply_lines`	No
`web_link_id`	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

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

addedOutput schema / properties / code
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / near_candidates

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "company_id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "company_id",
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / near_candidates_truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / reply_lines

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / url / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / url / type

Added value: +[
+  "string",
+  "null"
+]

Changed2 schema fields changedOct 21, 2026
- addedOutput schema / properties / url / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / url / type
```
Removed value: -"string"
```
AddedOct 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Goes beyond the annotations with the non-obvious disclosure that the returned web_link_id may differ from the one passed because another record already held the same link, plus the explicit success/failure return shape. It does not spell out the destructive consequence flagged by destructiveHint=true (whether the prior URL is lost or whether a deduplicated row is affected on the other record), leaving one meaningful gap.

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?

Front-loaded with the core action, then usage routing, then a REQUIRED/OPTIONAL block — a very readable shape. The REQUIRED list restates what the schema already enforces, which is mild redundancy, but nothing is padding.

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

Completeness4/5

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

An output schema exists, yet the description still summarizes the return, and it covers the identity-provenance of web_link_id that an agent would otherwise get wrong. The 9-param surface is heavy on workspace/conversation/idempotency plumbing, which the schema documents fully, so the remaining omission is mainly the destructive side effect.

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 baseline is 3, but the description adds real value: it tells the agent to obtain web_link_id via well_query_records on the parent, states the pass-at-least-one constraint on url/platform that the schema does not encode as anyOf, and maps platform enums to parent type. The platform-per-parent detail largely duplicates the schema's own note, which keeps it from a 5.

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 (Change), a bounded resource (one web link of a company or person in the current workspace), and enumerates what counts as a web link (website, LinkedIn, X/Twitter, GitHub, other profile URL). This cleanly separates it from the add/remove siblings without opening either schema.

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 says when to use it ("when the user asks to fix, replace or edit a link the record already has") and names both alternatives with their own trigger conditions: well_add_contact_channel for adding, well_remove_contact_channel for removing. No inference required.

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?