Skip to main content
Glama

Stop a shared link

well_revoke_share_links
DestructiveIdempotent

Stop a shared link made by well_share_widget, well_share_canvas, well_create_expense_group_link, or well_create_chat_invite_link, so it no longer opens for anyone, including from a message already sent. Call it when the person asks to stop, cancel, unshare or revoke a link to a figure, board, group's live balances, or a tracked WhatsApp chat link.

Pass exactly one of:

  • url: the link exactly as the person pasted it (it ends in /w/#s=<code>, /b/#s=<code>, or /g/#s=<code>).

  • share_link_id: the id the share returned, when the link was made earlier in this conversation, or an id well_list_share_links returned.

  • all: true, only when the person asks to stop every shared link of this workspace.

A member stops the links they made; a workspace owner or admin stops any link of the workspace, and all stops every link the caller may stop. A refusal says the link belongs to another member: tell the person that only its author or an owner or admin can stop it.

Never pass all to stop one link. When the person names a link you cannot identify, list the links with well_list_share_links first. This does not stop a document link in an email; that is another tool's link.

The shared content stays in Well, and a later share makes a new link; the stopped one never opens again. Tell the person plainly that the link no longer opens. When revoked_count is 0, say this workspace had no such link; never say a link was stopped.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
allNoTrue to stop every shared link of this workspace.
urlNoThe shared link the person pasted.
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.
share_link_idNoThe id the share or well_list_share_links returned for the link.
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
errorNo
messageNo
successYes
revoked_idsNo
revoked_countNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
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.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / resolved_workspace / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / resolved_workspace / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, it explains permissions (members stop their own links; owners/admins can stop any workspace link), refusal behavior, workspace scoping, and what happens to shared content after revocation. It also explains the `revoked_count` result and the rule against claiming a link was stopped when the count is zero.

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?

The description is long but well structured: purpose first, then when to use, then mutually exclusive parameter guidance, permissions, and output handling. Every paragraph carries operational value for a destructive seven-parameter tool.

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, multi-parameter tool with an output schema, the description covers the critical gaps: authorization boundaries, `all` misuse, workspace selection, fallback listing, and how to interpret a zero revocation count. The remaining parameter details are adequately covered by the 100%-descriptive input schema.

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 meaningful selection logic: pass exactly one of `url`, `share_link_id`, or `all`; `url` must be the pasted link including its `/w/#s=`, `/b/#s=`, or `/g/#s=` form; `all` is only for stopping every shared link in the workspace. It does not explain `conversation_id`, `idempotency_key`, or `workspace_scope`, but those are documented in the schema.

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 verb and resource: stop a shared link made by named tools so it no longer opens. It distinguishes this from document-link revocation and identifies the affected link types, so an agent can select it confidently.

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 explicitly says when to call it (stop, cancel, unshare, revoke), names the fallback well_list_share_links when the link cannot be identified, and excludes document links handled by another tool. It also clarifies that `all` must never be used to stop a single link.

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