Send a follow-up message
send_messageAdds a message to your conversation. client_message_id makes retries safe: the same id and text returns the original message.
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": {
"message": "<message>",
"client_message_id": "<client_message_id>",
"conversation_id": "<conversation_id>"
},
"name": "send_message"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | Follow-up message text. Max 4000 characters and 10240 UTF-8 bytes. | |
| conversation_id | Yes | conversation_id returned by start_conversation. | |
| client_message_id | Yes | Required idempotency key, unique per conversation. Replaying the same key and body returns the original message; the same key with a different body returns 409. | |
| conversation_token | No | conversation_token returned once by start_conversation. Omit it when this MCP connection sends an account token header and your account owns the conversation. |