Schedule Text Message
schedule_messageSchedule a message to be sent at a specific time in the future via Mobile Text Alerts API. Use this tool when you need to send a message at a later date/time rather than immediately. The message goes out from the account's default number (the one it last sent from) unless from names another; the response's sentFrom says which was used.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"to": "<to>",
"message": "<message>",
"scheduledDate": "<scheduledDate>"
},
"name": "schedule_message"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Recipient phone number (can be formatted as +1234567890, 234-567-8900, (234) 567-8900, etc.) | |
| from | No | Sending phone number. Omit to use the account's default (the number it last sent from). Use list_sending_numbers to see options. | |
| message | Yes | Message content to send | |
| scheduledDate | Yes | UTC date/time when the message should be sent. IMPORTANT: All times are interpreted as UTC regardless of format. Accepts: 'YYYY-MM-DD HH:MM:SS' (UTC), 'YYYY-MM-DDTHH:MM:SSZ', 'MM/DD/YYYY HH:MM' (UTC), etc. Example: '2024-12-25 14:00:00' means 2:00 PM UTC, not local time. Must be in the future. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | Raw Mobile Text Alerts API response envelope. A scheduled send returns a confirmation message only — there is currently no nested `data` payload and no scheduled-message ID. | |
| error | No | ||
| notice | No | Something the user should be told about this send, e.g. that it used a limited trial number | |
| status | Yes | ||
| context | No | Additional context about why the call was blocked | |
| success | Yes | ||
| sentFrom | No | The number the message was sent from | |
| errorCode | No | Machine-readable error code. 'ONBOARDING_REQUIRED' means the account has not finished brand registration. 'NO_SENDING_NUMBER' means no number on the account can send yet; 'SENDING_NUMBER_NOT_FOUND' / 'SENDING_NUMBER_UNAVAILABLE' mean the requested `from` number is not on the account or can't send. 'AUTH_FAILED', 'RATE_LIMITED', 'UPSTREAM_ERROR' and 'UPSTREAM_UNAVAILABLE' are Mobile Text Alerts API failures. | |
| nextSteps | No | Explicit recovery guidance for the calling agent | |
| statusText | Yes | ||
| scheduledFor | No | ||
| formattedPhone | No | ||
| totalScheduled | No |