NetBird
whatsapp_list
List WhatsApp messages, newest first, as a cursor page ({data, next_cursor, …}). Each message carries the one content it was built from: a template, or free-form text, image, video, audio, sticker, document or location. Pass next_cursor back as starting_after to fetch the next page. Filter by direction, status, recipient (to), sender (from), business-scoped user ID (bsuid), template category, or tag. to and from each accept a phone number or a business-scoped user ID; pair either with direction to search a single side of the message. Use whatsapp_get for one message's current state.
Remote bird/mcp
Remote (network-hosted)
Other tools also called whatsapp_list?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"to": {
"type": "string",
"description": "Filter by recipient, exact match. The recipient is the contact on an outbound message and your business number on an inbound one, matching the to each message returns. Accepts an E.164 phone number, or a business-scoped user ID to name the contact. Only a contact is ever identified by a business-scoped user ID, so to=<business-scoped user ID> matches outbound messages only."
},
"tag": {
"type": [
"null",
"array"
],
"items": {
"type": "string"
},
"description": "Filter by tag. Accepts name to match any record carrying that tag name, or name:value to match a specific tag pair (for example category:welcome). Repeat the parameter to add more tags. A record must match every tag listed to be returned."
},
"from": {
"type": "string",
"description": "Filter by sender, exact match. The sender is your business number on an outbound message and the contact on an inbound one, matching the from each message returns. Accepts an E.164 phone number, or a business-scoped user ID to name the contact. Only a contact is ever identified by a business-scoped user ID, so from=<business-scoped user ID> matches inbound messages only."
},
"bsuid": {
"type": "string",
"description": "Filter by business-scoped user ID (Meta identifier), matching the contact in either direction. to and from also accept one, but each matches a single end of the message."
},
"limit": {
"type": "integer",
"description": "Maximum number of items to return per page."
},
"status": {
"type": [
"null",
"array"
],
"items": {
"type": "string",
"examples": [
"scheduled",
"accepted",
"sent",
"delivered",
"failed",
"rejected",
"canceled",
"received"
]
},
"description": "Filter by status. Repeat the parameter to match any of several statuses."
},
"category": {
"type": "string",
"description": "Filter by category."
},
"direction": {
"type": "string",
"examples": [
"outbound",
"inbound"
],
"description": "Filter by whether the business sent the message (outbound) or received it from the contact (inbound)."
},
"phone_number": {
"type": "string",
"description": "Deprecated: use to or from instead, which also match a business-scoped user ID. Filters by contact phone number (E.164 exact match), in either direction."
},
"created_after": {
"type": "string",
"description": "Limits the response to resources created at or after this timestamp. Combine it with created_before to select a time window. Use an RFC 3339 timestamp with a timezone offset."
},
"ending_before": {
"type": "string",
"description": "Cursor from the prev_cursor or refresh_cursor field of a previous list response. Returns items immediately before the cursor position in the current sort order. prev_cursor returns the preceding page. refresh_cursor anchors at the first row of that response, which on a newest-first sort is how to fetch the items that have appeared since."
},
"created_before": {
"type": "string",
"description": "Limits the response to resources created before this timestamp. Combine it with created_after to select a time window. Use an RFC 3339 timestamp with a timezone offset."
},
"starting_after": {
"type": "string",
"description": "Cursor from the next_cursor field of a previous list response. Returns items immediately after the cursor position in the current sort order."
}
}
}