List given links
well_list_given_linksList every link the workspace has given out that still opens, in one read: the workspace invitation, the customer pages of invoices, the links of draft invoices, the document links sent by email, the board and widget shares, and the person's own linked WhatsApp number. It reads only: it makes, changes and stops no link.
Call it when the person asks which links they gave, what is shared, or what is still open to people outside, in any language ("Which links did I give?", "Quels liens ai-je donnés ?"). Call it at once: never ask which kind of link they mean, since this one read lists every kind. Never call well_get_workspace_invite_link or well_get_invoice_draft_link to answer that: they make a link.
Each row says what the link opens (opens), its name (label) and who holds it (holder_kind and holder): the role the invitation gives, the invoice's customer, the number of links of a share (link_count), or the person's own number. The links of one board are one row. Nothing counts who opened a link, so never say how many people opened one.
Answer with one numbered line per row, under the total of rows and the workspace name. Never show a URL, a token or an id: when the person wants a link itself, the tool of that kind gives it. With more_count above zero, end with "and N others". With no row, say no link is open on the workspace.
A member sees the shares they made and their own WhatsApp number; an owner or admin also sees the invitations, the invoice pages and the document links.
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
| Name | Required | Description | Default |
|---|---|---|---|
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which. | |
| conversation_id | No | The 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. | |
| workspace_scope | No | Restrict 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
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| links | No | The live links, newest first, at most 20; your own WhatsApp number last. | |
| success | Yes | ||
| more_count | No | How many more live links exist beyond the rows shown. | |
| workspace_name | No | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| newly_connected | No | 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. | |
| resolved_workspace | No | The workspace that answered, when the caller named none and the token authorizes several. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. | |
| more_count_is_lower_bound | No | True when the workspace has more shares than one read holds, so `more_count` is a minimum. |