Message: Send native media
message_send_native_mediaSend one media/file attachment using the provider's native rendering mode where supported. Resolve chat_id first. Provide padded base64 bytes; uploads use multipart when the complete JSON exceeds 1 MiB. Provider file limits still apply. Useful for inline image/video/native media; for WhatsApp multiple attachments may become separate provider messages, so this tool intentionally sends one attachment per call for predictable behavior.
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": {
"chat_id": "<chat_id>",
"content_base64": "<content_base64>",
"content_type": "<content_type>",
"filename": "<filename>"
},
"name": "message_send_native_media"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | No | ||
| chat_id | Yes | Exact chat.id resolved/listed for the destination conversation; never pass a person name/user_id here. | |
| filename | Yes | ||
| account_id | No | Optional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here. | |
| content_type | Yes | ||
| content_base64 | Yes |