Messaging: Resolve recipient
messaging_resolve_recipientTurn a person's name, nickname, phone number or handle into the exact WhatsApp/Instagram/Facebook/Telegram recipient BEFORE sending: searches the user's 1-to-1 chats (ranked by most recent exchange) and contacts. Returns incomplete (lookup could not be fully enumerated; do not send automatically), resolved (one clear match: send immediately with the recommended next tool, no extra confirmation needed when the user already gave the message), ambiguous (several people: ask which one, most recent conversation first) or not_found. Use for 'send a WhatsApp to Julien', 'reply to Marie on Instagram', 'message +33 6…'. Never pass a name as chat_id or user_id.
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": {
"provider": "<provider>",
"name": "<name>"
},
"name": "messaging_resolve_recipient"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | How the user refers to the person: first name, full name, phone number or handle. | |
| inbox_id | No | Required for Facebook: exact personal or PAGE_<id>_INBOX inbox.id from facebook_list_inboxes. Preserves the sending identity. Omit for other providers. | |
| provider | Yes | Messaging provider named by the user. LinkedIn recipients use linkedin_resolve_person + linkedin_start_conversation instead. | |
| account_id | No | Optional Nilyo connection ID (unipile_account_id from list_connected_accounts). Required when the user has several accounts for the provider: pick the one the user named. |