Draft, compose, and send an email the user confirms in a review card or composer. Use this tool whenever the user asks you to draft, write, compose, or send an email (or reply to one) from the agent session view or from chat — never write the email as plain text there. It opens the draft for the user to review, edit, and confirm before it is sent, so it is the correct tool even when the user only wants a draft. Do NOT use it for a prompt that came from a channel or document thread — the context block names a conversation parent when it did, and there is no surface to review a draft in: write the email out in your reply, ask whether to send it, and use SendConfirmedEmail once the user approves. To reply to an existing message, provide the replying_to_id. Write the body in Markdown — use bold, italics, lists, links, and other standard Markdown formatting. The draft composer renders the Markdown for the user to review and edit; the composer produces HTML that is sent as the actual email body.
The body of the email, written as Markdown. A host with a composer (chat) replaces this with the base64url-encoded HTML the composer exported before the tool runs; a host without one (an agent session) leaves the Markdown, and this tool renders it the same way.
to
EmailRecipient[]
Yes
The primary recipients (To field).
cc
EmailRecipient[]
No
Carbon copy recipients (optional).
bcc
EmailRecipient[]
No
Blind carbon copy recipients (optional).
replyingToId
string
No
The ID of a message to reply to (optional). When set, the email is sent as a reply within the same thread.
includeSignature
boolean
No
Per-message signature override, set by the composer’s signature preview — not normally by you. Omit to use the inbox’s default policy (always on a new email; on replies/forwards only when the user enabled it). false excludes the signature for this one email.
