Skip to main content
Glama

Delete whatsapp link

well_delete_whatsapp_link
Destructive

Log the user out of WhatsApp. This is the way to log out of WhatsApp or unlink a number: it removes the link between the user's WhatsApp number and their Well login, in every workspace of that login. The next message from that number gets a fresh sign-up link. The user's phone stays on their profile.

Call it when the user asks to log out of WhatsApp, unlink or disconnect their number, or start fresh on WhatsApp, in any language. Examples: "log me out of WhatsApp", "unlink my number", "disconnect my WhatsApp", "start fresh on WhatsApp", "déconnecte-moi de WhatsApp", "me déconnecter de WhatsApp", "délier mon numéro", "repartir de zéro sur WhatsApp". Never tell the user this cannot be done. It is not for starting a new conversation topic, and not for disconnecting a connector.

Omit person_id for the user's own number. An owner or admin who asks to unlink another member's WhatsApp passes that member's person_id: it removes the number that member proved in this workspace only. Anyone else is refused.

The result is status "unlinked" with how many links were removed, or "not_linked" when no number was linked. When still_reaches_workspace is true, the member proved the same number in another workspace, so it still reaches this workspace: tell the user so, and do not say the member is logged out here.

Input Schema

NameRequiredDescriptionDefault
person_idNoThe member whose number to unlink, for an owner or admin. Omit it for the user's own number.
workspace_idNoTarget 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_idNoThe 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_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict 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

NameRequiredDescriptionDefault
codeNo
errorNo
statusNo
successYes
reply_linesNo
unlinkedCountNoHow many WhatsApp links were removed.
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
near_candidatesNo
newly_connectedNoTools 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_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.
still_reaches_workspaceNoThe number still reaches this workspace through a link the member proved in another workspace.
near_candidates_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / person_id
      Added value: +{
      +  "description": "The member whose number to unlink, for an owner or admin. Omit it for the user's own number.",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / still_reaches_workspace
      Added value: +{
      +  "description": "The number still reaches this workspace through a link the member proved in another workspace.",
      +  "type": "boolean"
      +}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark this as destructive and non-read-only, but the description adds substantial context: exactly what link is removed, that it spans every workspace of the login, that the phone stays on the profile, that the next message gets a fresh sign-up link, and that other users are refused. It also explains the `still_reaches_workspace` edge case so the agent does not falsely tell a member they are logged out.

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?

The description is front-loaded with purpose and primary triggers, and every section has a clear role. It is somewhat long due to the multilingual examples and behavioral edge cases, but those examples directly support accurate tool selection.

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 a destructive unlink operation with an output schema, the description covers trigger phrases, exclusions, permission behavior, workspace scoping, result statuses, and the `still_reaches_workspace` caveat. It gives the agent everything needed to call the tool correctly and communicate the outcome accurately.

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 schema already documents all five parameters. The description still adds meaningful semantics for person_id, including that an owner/admin unlink applies only to the number proved in this workspace and that unauthorized callers are refused, though it does not discuss workspace_id, conversation_id, idempotency_key, or workspace_scope.

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?

The description states a specific action and resource: logging the user out of WhatsApp by removing the link between their WhatsApp number and Well login across every workspace. It also distinguishes this from adjacent actions, explicitly saying it is not for starting a new conversation topic and not for disconnecting a connector.

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?

It gives explicit trigger conditions ('log out of WhatsApp', 'unlink or disconnect their number', 'start fresh') with multilingual examples, plus clear exclusions. It also explains the owner/admin scenario for passing another member's person_id and when someone is refused.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources