Send a text message
send_messageSends a real iMessage/SMS from the owner's number to a phone number, email or existing chat: text, a file, or both. The file is either an attachment from a message (attachment_id, to forward it) or a new file you write (file).
Instructions
Sends a real iMessage/SMS from the owner's number to a phone number, email or existing chat: text, a file, or both. The file is either an attachment from a message (attachment_id, to forward it) or a new file you write (file). The server delivers only to recipients on its allowlist and enforces a length limit, file rules (files must be turned on; no programs or archives) and a rate limit; the result says whether the sent message was confirmed in history. Each call is a destructive action that the client asks the user to approve.
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 |
|---|---|---|---|
| to | No | Recipient as an E.164 phone number (+14155550123) or email. Give either `to` or `chat_id`. | |
| file | No | A new file to send, up to 5 MB: its name and its content as text or base64. Needs files turned on (get_status: send.files). | |
| text | No | The exact message text the user approved. Up to the server's max_chars (1,000 by default; see get_status). Optional when sending a file. | |
| chat_id | No | Existing chat id from list_chats (works for group chats). Give either `to` or `chat_id`. | |
| attachment_id | No | Send this attachment, for example to forward a photo: the "id" of an entry in a message's attachments list. Needs files turned on (get_status: send.files). |