Skip to main content
Glama

Get the workspace invitation link

well_get_workspace_invite_link
Idempotent

Return the link that lets people join the user's OWN workspace, when the user asks for an invitation link into their account or workspace and names no person and no email address. When the user names one person or one address, use well_invite_members with delivery: "link" instead. For a link that lets someone open their own account on Well, use well_get_general_invite_link. When the user does not say which of the two links they mean, ask them before any call.

Pass role: admin or member, the role the link gives, when the user named it; never pick it for them. On WhatsApp, when the user named no role, leave role out: Well's card asks the role, and the role the person picks is their yes. On any other surface, ask the user which role before the call.

workspace_link: every person who opens it joins THIS workspace with role. It works for any number of people and has no expiry. The same role always returns the same link, and the admin link and the member link are two different links.

Only an owner or admin of a company workspace gets a workspace link. Otherwise workspace_link is absent, workspace_link_refusal names why (INSUFFICIENT_PERMISSIONS, DEMO_WORKSPACE for sample data, MEMBERSHIP_WORKSPACE for the person's own space, or LINK_UNAVAILABLE), and general_link carries the general link to Well, to offer in its place. Pass language, the language of the conversation, for the greeting that link carries.

When the user asks to stop the workspace link of a role, use well_delete_workspace_invite_link instead.

Input Schema

NameRequiredDescriptionDefault
roleNoThe role the workspace link gives: admin or member. Left out on WhatsApp when the user named none, so Well's card asks it; elsewhere ask the user first.
languageNoThe language of the conversation, for the greeting of the general link a refusal offers. Defaults to English.
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
roleNoThe role the call names. Absent only when the call named none.
errorNo
successYes
general_linkNoPresent only when a workspace link is refused and Well has a WhatsApp number: the general link, to offer in its place. It opens the WhatsApp chat with Well, and a person who uses it gets their own workspace, not this one.
workspace_idNo
workspace_linkNoPresent only when the workspace gives a link. Every person who opens it joins the workspace with `role`. It has no expiry and works for any number of people, until the user asks to stop it. Give it to the user exactly as returned.
workspace_nameNoThe name of the workspace the link opens. 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_refusalNoPresent only when the call gives no workspace link. INSUFFICIENT_PERMISSIONS: the caller is not an owner or admin of the workspace. DEMO_WORKSPACE: the workspace holds sample data. MEMBERSHIP_WORKSPACE: the workspace is the person's own space, and a workspace link exists only for a company workspace. LINK_UNAVAILABLE: the link cannot be shown again, so stop it with well_delete_workspace_invite_link and ask for a new one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / role / description
      Previous value: -"The role the workspace link gives: admin or member. Ask the user when they named none."New value: +"The role the workspace link gives: admin or member. Left out on WhatsApp when the user named none, so Well's card asks it; elsewhere ask the user first."
    • removedInput schema / required
      Removed value: -[
      -  "role"
      -]
    • changedOutput schema / properties / role / description
      Previous value: -"The role the call names."New value: +"The role the call names. Absent only when the call named none."
    • changedOutput schema / required
      Previous value: -[
      -  "role",
      -  "success"
      -]New value: +[
      +  "success"
      +]
  2. Changed4 schema fields changed
    • removedInput schema / properties / action
      Removed value: -{
      -  "description": "Defaults to \"get\", which returns the links. Pass \"revoke\" to stop the workspace link of this role.",
      -  "enum": [
      -    "get",
      -    "revoke"
      -  ],
      -  "type": "string"
      -}
    • changedOutput schema / properties / workspace_link / description
      Previous value: -"Present only when action is \"get\" and the workspace gives a link. Every person who opens it joins the workspace with `role`. It has no expiry and works for any number of people, until the user asks to stop it. Give it to the user exactly as returned."New value: +"Present only when the workspace gives a link. Every person who opens it joins the workspace with `role`. It has no expiry and works for any number of people, until the user asks to stop it. Give it to the user exactly as returned."
    • changedOutput schema / properties / workspace_link_refusal / description
      Previous value: -"Present only when the call gives no workspace link, or may not stop one. INSUFFICIENT_PERMISSIONS: the caller is not an owner or admin of the workspace. DEMO_WORKSPACE: the workspace holds sample data. MEMBERSHIP_WORKSPACE: the workspace is the person's own space, and a workspace link exists only for a company workspace. LINK_UNAVAILABLE: the link cannot be shown again, so stop it (action revoke) and ask for a new one."New value: +"Present only when the call gives no workspace link. INSUFFICIENT_PERMISSIONS: the caller is not an owner or admin of the workspace. DEMO_WORKSPACE: the workspace holds sample data. MEMBERSHIP_WORKSPACE: the workspace is the person's own space, and a workspace link exists only for a company workspace. LINK_UNAVAILABLE: the link cannot be shown again, so stop it with well_delete_workspace_invite_link and ask for a new one."
    • removedOutput schema / properties / workspace_link_revoked
      Removed value: -{
      -  "description": "Present only when action is \"revoke\" and the caller may stop the link. True when a live link was stopped: it admits nobody from now on. False when no link was live for this role.",
      -  "type": "boolean"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / properties / newly_connected / description
      Previous value: -"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. Start the reply with 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."New value: +"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."
  4. 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: it discloses the permission gate (only owner/admin gets a workspace link), the enumerated refusal codes (INSUFFICIENT_PERMISSIONS, DEMO_WORKSPACE, MEMBERSHIP_WORKSPACE, LINK_UNAVAILABLE), the fallback via general_link, and link lifetime/multiplicity semantics (any number of people, no expiry, deterministic per role, admin ≠ member link). The 'same role always returns the same link' claim is consistent with idempotentHint=true.

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?

Long and dense, but front-loaded with the core purpose and disambiguation before the parameter and refusal detail. Each paragraph is scoped to a distinct concern, though the surface-specific role handling is verbose enough that a tighter phrasing could carry the same rules.

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?

Even though an output schema exists, the description supplies the interpretation an agent needs for the refusal path (why a refusal fires and what to offer instead) and the surface-dependent role handling, which are not self-evident from structured fields. Nothing needed to call it correctly is missing.

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 meaning: it explains that role is never to be picked for the user, that on WhatsApp it should be omitted so Well's card asks, that it must be asked elsewhere before the call, and that language drives the greeting of the refusal's general link. Only workspace_scope lacks any extra prose.

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 precise verb+resource ('return the link that lets people join the user's OWN workspace') and immediately distinguishes it from the two near-identical siblings, well_invite_members (with delivery:"link") and well_get_general_invite_link. An agent can route correctly without opening any 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 gives the when (user asks for a workspace invite link naming no person/email), the when-not (one person or address named → use well_invite_members), the alternative (well_get_general_invite_link for a self-account link), the ambiguity rule (ask before any call), and the stop-link case (well_delete_workspace_invite_link). Comprehensive routing guidance.

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