Skip to main content
Glama

Delete the workspace invitation link

well_delete_workspace_invite_link
DestructiveIdempotent

Stop the workspace link of one role, when the user asks to stop, cancel or delete the invitation link into their own workspace. From then on the link admits nobody. The people who already joined through it stay in the workspace.

Pass role: admin or member, the role of the link to stop. Ask the user which role when they named none.

workspace_link_deleted is true when a link was stopped and false when no link was live for that role. A later well_get_workspace_invite_link for that role makes a new link, and the stopped one never works again. Only an owner or admin of the workspace may stop a link; otherwise workspace_link_refusal is INSUFFICIENT_PERMISSIONS and nothing changes.

Input Schema

NameRequiredDescriptionDefault
roleYesThe role of the workspace link to stop: admin or member.
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
roleYesThe role the call names.
errorNo
successYes
workspace_idNo
workspace_nameNoThe name of the workspace the link opened. Absent when the caller is not an owner or admin of it.
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.
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.
workspace_link_deletedNoPresent when the caller may stop the link. True when a live link was stopped: it admits nobody from now on, and the people who already joined stay. False when no link was live for this role.
workspace_link_refusalNoPresent when the caller is not an owner or admin of the workspace, so no link was stopped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: annotations only cover destructive/idempotent/closed-world, while the description discloses that existing joiners remain, that the result is true/false depending on whether a live link existed, that the stopped link is permanently dead, and that owner/admin is required with INSUFFICIENT_PERMISSIONS otherwise.

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?

Purpose is front-loaded and each paragraph carries useful constraint information. Slight redundancy in describing return fields (workspace_link_deleted, workspace_link_refusal) that the output schema already covers, but it is not wasteful.

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, permission-gated mutation with an output schema present, the description supplies the permission model, the consequence for existing members, the irreversibility, and the role requirement — everything the agent needs beyond structured fields.

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; the description adds actionable meaning for the required role param, including its two values and the instruction to ask the user when unspecified. It adds prompt-level guidance but little beyond the schema for the other parameters.

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+resource+scope: 'Stop the workspace link of one role.' It names the sibling well_get_workspace_invite_link as the thing that regenerates a link, so an agent can distinguish this teardown tool from link creation/retrieval without opening schemas.

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?

Explicit trigger ('when the user asks to stop, cancel or delete the invitation link into their own workspace'), explicit alternative (well_get_workspace_invite_link makes a new link), and explicit disambiguation for the required role param ('Ask the user which role when they named none').

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