NetBird
whatsapp_stats_by_phone_number
Outbound WhatsApp counts grouped by the business number that sent them, ranked by accepted volume, each row marked as a number your workspace connected or one Bird manages on your behalf. Use it to find the sender behind a delivery problem, then read that number's own state from `whatsapp_numbers_list` filtered by `phone_number`: a row carries the number itself, not its `wan_` id. Rows are the whole workspace's: the breakdown takes no dimension filter.
Remote bird/mcp
Remote (network-hosted)
Other tools also called whatsapp_stats_by_phone_number?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"to": {
"type": "string",
"description": "Inclusive end of the window, a calendar day (YYYY-MM-DD). Interpreted in timezone, or UTC when omitted. Max window 365 days. Defaults to today in that timezone when omitted."
},
"from": {
"type": "string",
"description": "Inclusive start of the window, a calendar day (YYYY-MM-DD). Interpreted in timezone, or UTC when omitted. Must not be after to. Max window 365 days. Defaults to 30 days before to when omitted."
},
"limit": {
"type": "integer",
"description": "Maximum number of phone-number rows to return, ranked by accepted volume descending."
},
"timezone": {
"type": "string",
"description": "IANA timezone identifier used to group statistics, for example Asia/Kathmandu. The default is UTC. Day and hour boundaries, including the default window when from and to are omitted, follow this timezone. When this parameter is set, pass from and to as calendar days or Z instants instead of timestamps with explicit UTC offsets."
}
}
}