List connector tools
well_list_connector_toolsDiscover the actions a connected provider exposes (e.g. "what can I do with Attio?").
WORKFLOW:
well_list_connectors() → pick the connected provider (connection_status "enabled" or "processing": a connection whose sync was started still serves its tools) and read its workspace_connector_id directly off the row.
well_list_connector_tools({ workspace_connector_id }) → the actions that provider offers (name + description + input schema).
well_invoke_connector_tool({ workspace_connector_id, tool, args }) → run one, shaping args from the input schema returned here.
Use this whenever you don't already know a connector's tool names — never guess them.
Each tool carries read_only. On a server this workspace added, a tool whose read_only is false and that the server does not mark as changing data stays unread until an owner or admin declares it read-only with well_update_custom_connector.
A provider can expose hundreds of tools, so the whole list is large. When you already know the name of the one tool you need, pass it as tool: the result then carries that one tool with its input schema, or an empty tools list with success true when the connection does not expose it.
Every response also carries reconnect_url: a deep link to the connector's setup page in the web app. When success is false or status is "need_reconnect" (the provider's token is stale/revoked, so no tools come back), give the user reconnect_url so they can re-authenticate the connector. Surface it as a clickable link; never invent connector URLs.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tool | No | Return only this one tool, with its description and input schema. | |
| workspace_id | No | Target workspace. This read reports one workspace's own data. Omit it and the token's primary workspace answers, which may not be the one you mean; the result names the workspace that did. | |
| 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. | |
| workspace_connector_id | Yes | The connected provider's workspace_connector_id (from well_list_connectors). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| tools | No | ||
| total | No | ||
| status | No | ||
| success | Yes | ||
| error_code | No | ||
| usage_notes | No | ||
| reconnect_url | No | ||
| connector_name | No | ||
| connector_slug | 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. |