well_send_email_draft

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

Save the final text of an email draft into the user's own Gmail drafts, or hand it to the user's own email app. Well sends nothing itself. The card that `well_draft_email` shows calls this when the user presses Send. Do not call it yourself to send on the user's behalf. Draw the card with `well_draft_email` and let the user press Send. REQUIRED: `to` (at least one address), `subject` and `body_lines` (the paragraphs), all exactly as the user last saw them. `attachment_ids` are `document_id`s of this workspace. Pass the card's `draft_id` unchanged: it keys the durable write, so a second press of the same card replays the first result and never creates a second draft. Returns `status: "draft_created"` (with `mailbox_address` and `gmail_drafts_url`) when a Gmail draft now waits in the member's mailbox, `"draft_queued"` when the write is still owed, or `"mailto"` with a `mailto_url` — and a `fallback_reason` when the Gmail path declined. Every status carries `mailto_url`: on `draft_queued` the card keeps it as the way out, and a call after the owed write gave up answers `mailto` with the reason, so the member always keeps a way to send. `sent` is false on every one of them: the member sends the draft, never Well. The attached documents travel as the download links the body already carries, which do not expire while the document exists. Well sent nothing, so never tell the user the email was sent. A failure carries an `error_reason`; 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.