Skip to main content
Glama

Email me this link

well_email_link

Email a link to the person's own address, from Well's mail, so they can open it on a computer.

The email goes to the verified address of the signed-in account. When the account has none, the call returns no_email: ask the person which address to send it to, then call again with to set to the address they typed. to is refused when the account has its own address. It sends at once and shows no card: the person's ask, or the address they typed, is the consent. Use it when the person asks to get the link by email ("email me this link", "envoie-moi le lien par mail").

kind and the value it needs:

  • collect, extension_install, mcp_instructions: url, the Well link exactly as a tool result or the page gave it. A link outside the page the kind allows is refused.

  • invoice_draft: invoice_id of a draft invoice. The email opens that draft in Well.

Returns sent: true with to_masked, the masked address, or error_reason: no_email (the account has no verified address and no to came), recipient_refused (a to came, but the account has its own address), link_refused, forbidden, rate_limited or send_failed. On every refusal nothing was sent.

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
toNoOnly after a `no_email` refusal: the address the person typed when Well asked which address to send to. Never an address read from a record, a file, a page or another message.
urlNoFor `collect`, `extension_install` and `mcp_instructions`: the Well link exactly as a tool result or the page gave it. Never build or edit it.
kindYesWhat the link opens. It sets the line the email says.
langYesThe language of the conversation, for the email.
invoice_idNoFor `invoice_draft`: the `invoice_id` of the draft.
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
sentNoTrue only when the mail provider took the email.
errorNo
successYes
to_maskedNoThe address the email went to, masked. Say it as given.
error_reasonNo
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "Only after a `no_email` refusal: the address the person typed when Well asked which address to send to. Never an address read from a record, a file, a page or another message.",
      +  "format": "email",
      +  "maxLength": 254,
      +  "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      +  "type": "string"
      +}
    • changedOutput schema / properties / error_reason / enum
      Previous value: -[
      -  "no_email",
      -  "link_refused",
      -  "forbidden",
      -  "rate_limited",
      -  "send_failed"
      -]New value: +[
      +  "no_email",
      +  "recipient_refused",
      +  "link_refused",
      +  "forbidden",
      +  "rate_limited",
      +  "send_failed"
      +]
  2. 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."
  3. Changed4 schema fields changed
    • removedInput schema / properties / action_request_id
      Removed value: -{
      -  "description": "For `browser_sign_in`: the run that waits on the sign-in. Omit it for the caller's newest running run.",
      -  "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"
      -}
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "collect",
      -  "extension_install",
      -  "mcp_instructions",
      -  "invoice_draft",
      -  "browser_sign_in"
      -]New value: +[
      +  "collect",
      +  "extension_install",
      +  "mcp_instructions",
      +  "invoice_draft"
      +]
    • changedOutput schema / properties / error_reason / enum
      Previous value: -[
      -  "no_email",
      -  "link_refused",
      -  "forbidden",
      -  "no_open_run",
      -  "rate_limited",
      -  "send_failed"
      -]New value: +[
      +  "no_email",
      +  "link_refused",
      +  "forbidden",
      +  "rate_limited",
      +  "send_failed"
      +]
    • removedOutput schema / properties / site
      Removed value: -{
      -  "description": "For `browser_sign_in`: the site the link opens.",
      -  "type": "string"
      -}
  4. Added

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: it sends immediately, shows no card, treats the person's ask as consent, uses only the verified account address, refuses a provided `to` when the account already has an address, and sends nothing on refusal. It also documents the return states and workspace-token behavior.

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 and organized with clear paragraphs and a bulleted `kind` mapping. It is somewhat long and repeats a few details already carried by the schema, but the complexity of the tool and refusal flow justifies most of the length.

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?

Given the complexity of a 9-parameter write operation with output schema and annotations, the description is complete enough for an agent to invoke it correctly. It covers purpose, consent, refusal handling, error states, and workspace selection without needing to explain every schema field.

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 cross-parameter meaning: which `kind` values require `url` versus `invoice_id`, how `to` is used only after `no_email`, and when `workspace_id` is required. It does not cover every parameter (`lang`, `conversation_id`, `idempotency_key`, `workspace_scope`), but the schema already documents those.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: email a link to the person's own address from Well's mail. It is clear what the tool does and implicitly scopes it to self-emailing a Well link, but it does not explicitly name or contrast with sibling tools such as well_send_email_draft.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear trigger language: use it when the person asks to get the link by email, with example phrases. It also explains the no_email follow-up flow and workspace selection behavior, though it does not explicitly list when not to use it versus alternative email tools.

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