Send an email
send_messageSend an email directly from your Gmail account, with optional CC/BCC, plain-text or HTML body, and thread replies.
Instructions
Sends an email from the authenticated mailbox, immediately and irreversibly. Requires at least one recipient across to/cc/bcc (a bcc-only send is fine — to may be omitted) and at least a subject or a body; body_text and body_html together become multipart/alternative. TO REPLY IN A THREAD: call get_message on the message being answered first, then pass its threadId as thread_id, its headers.messageId as in_reply_to, and the same subject prefixed with "Re: " — Gmail threads the reply only when all three line up. Returns the sent message's id, threadId and labelIds. NEVER retried after a timeout or 5xx (a duplicate email cannot be unsent): if the outcome is unclear, search list_messages with in:sent before considering a re-send. Everyday accounts can send ~500 emails/day (Workspace ~2000); exceeding it disables sending for hours.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "send_message"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cc | No | Carbon-copy recipients. | |
| to | No | Primary recipients. Optional when cc or bcc carries at least one recipient (bcc-only send). | |
| bcc | No | Blind-copy recipients. | |
| subject | No | The subject line. For replies use the original subject with "Re: ". | |
| body_html | No | HTML body (sent as multipart/alternative when body_text is also set). | |
| body_text | No | Plain-text body. | |
| thread_id | No | Reply into this thread (pair with in_reply_to and a matching subject). | |
| references | No | Explicit References header chain (defaults to in_reply_to). | |
| in_reply_to | No | RFC Message-ID of the message being replied to (headers.messageId from get_message). |