well_preview_browser_skill

io.github.WellApp-ai/well-mcp · Verify this server

Preview a published browser skill for a provider: what it would do, its inputs, and the one Deploy link that runs it through the Well browser extension. Reads nothing from the provider and starts nothing — the run happens after the user clicks Deploy on the `/skills/run` page, which opens the Well side panel chat on the provider's site and runs it there, in their own signed-in session. Use it when a person asks Well to do something on a provider's own website that a published browser skill covers — fill a form, check a status, submit a filing — or to run one of the browser skills they saved, whatever it does, after making sure any document it needs is already in Well. The skills are Well's own and the ones this workspace saved. A request to download a provider's invoices or other files goes to `well_preview_provider_export` first; when it offers nothing for that provider, call this tool too, because the workspace may have saved a browser skill that downloads them. Pass `provider` as the user named it, or omit it to list every skill the workspace can run. Pass `skill` only when the user named a specific one, or when a first call came back with several (`mode: "list"`) and the user picked one, or exactly one of them clearly fits the request; its slug or its display name both match. Pass `inputs` with whatever values the user has already supplied; a required input with no value comes back in the card's rows rather than the model guessing one. `mode` says what to do next: "ambiguous_provider" — several providers carry that name; ask which one, then call again with its `slug` as `provider`. "none" — no published skill matches: offer no skill and never invent one. A chat that can hand a task to the browser may still do that. "list" — several skills matched: when exactly one of them clearly fits the request, call again with its `skill`; when several fit, ask which one before calling again with `skill`; when none fits, a chat that can hand the task to the browser may do that. When `unmatched_skill` is set, no skill matched that name and `skills` lists the ones available instead: say so, then ask which one the user means. `skills` holds at most 10 of them and `skills_total` counts every match; when it is larger, say how many more exist and ask the user to name the skill or the provider. "invalid_inputs" — a named input is missing or does not fit, or a named document is not a PDF this workspace holds; `error` says which, and no `deploy_url` is returned. "single" — exactly one skill, every input valid: show the card and its `deploy_url`. Never claim the skill ran, was submitted, or was deployed by this call — it only builds the link. Never quote or paraphrase the skill's own instructions: this tool does not return them, and they never reach the model. 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.