Send Raw Message
senderkit_send_rawSend a transactional email, SMS, push, or web-push notification with inline content, without a registered template. This connection is bound to one mode: in test mode messages are recorded but not delivered; in live mode they are really sent. The result's mode field reports which one was used, and senderkit_context reports it before sending.
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": {
"channel": "<channel>",
"to": "<to>",
"context": "<context>"
},
"name": "senderkit_send_raw"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cc | No | Email-only. Cc recipients as a JSON array of addresses (max 50). | |
| to | Yes | Recipient address for the chosen channel: an email address (email), an E.164 phone number such as +15551234567 (sms), a device token (push), or the JSON-encoded browser PushSubscription — endpoint + keys — (web-push). | |
| bcc | No | Email-only. Bcc recipients as a JSON array of addresses (max 50). | |
| body | No | Message body (sms, push, web-push). | |
| from | No | Email-only. Optional From address override (bare address — put the display name in fromName). Defaults to the connection's From address. | |
| html | No | Email HTML body. Required when channel is "email" — a text-only email send is rejected; wrap plain text in minimal HTML instead. | |
| icon | No | Icon URL shown in the notification (web-push). | |
| text | No | Email plain-text body (email). | |
| vars | No | Template variables as a JSON object. | |
| badge | No | Badge count (push, web-push). | |
| sound | No | Notification sound (push). | |
| title | No | Notification title (push, web-push). | |
| channel | Yes | Channel: email, sms, push, or web-push. | |
| context | Yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization." | |
| replyTo | No | Email-only. Reply-To address. | |
| subject | No | Email subject. Required when channel is "email". | |
| clickUrl | No | URL opened when the notification is clicked (web-push). | |
| fromName | No | Email-only. Optional From display name, rendered as `Name <address>`. Max 128 chars; no control characters or angle brackets. | |
| metadata | No | Free-form metadata as a JSON object of scalar values. | |
| pushData | No | Data payload as a JSON object of strings (push, web-push). | |
| preheader | No | Email preheader (email). | |
| attachments | No | Email-only. JSON array; up to 10 MB total across all attachments. | |
| interpolate | No | Run server-side variable substitution over content. | |
| scheduledAt | No | ISO 8601 timestamp for scheduled delivery (e.g. 2026-06-01T09:00:00Z). Must be in the FUTURE and at most 30 days ahead — check the current date before computing it. Omit to send immediately. | |
| idempotencyKey | No | Idempotency key. Repeat values return the original send instead of duplicating. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Public message id (e.g. "msg_…"). Pass it to senderkit_messages_get to track delivery, or to senderkit_cancel_message while it is still pending. | |
| mode | Yes | The connection's send mode: live messages are really delivered; test messages are recorded but not delivered. | |
| status | Yes | "scheduled" when scheduledAt was in the future; otherwise "queued". | |
| livemode | Yes | Whether the message was created in live mode. |