NetBird
whatsapp_stats_inbound_summary
Aggregate count of the WhatsApp messages your workspace received in one window, with the delta against the window immediately before when `compare` is set to `previous_period`. Inbound is counted separately from outbound: this answers "how much are customers writing to us", where `whatsapp_stats_summary` answers "how much are we sending".
Remote bird/mcp
Remote (network-hosted)
Other tools also called whatsapp_stats_inbound_summary?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"to": {
"type": "string",
"description": "Inclusive end of the window, in the same form as from. Defaults to today, or the current hour for an hour window. A day window may not exceed 365 days and an hour window 720 hours."
},
"from": {
"type": "string",
"description": "Inclusive start of the window, either a calendar day (YYYY-MM-DD) or an RFC 3339 instant rounded down to the hour. The form you use selects the grain the total is resolved at. Interpreted in timezone, or in UTC when timezone is omitted. Must use the same form as to. A numeric UTC offset (for example +05:45) is rejected when timezone is set; pass a calendar day or a Z instant instead. Defaults to 30 days before to for day windows, or 168 hours before to for hour windows."
},
"compare": {
"type": "string",
"examples": [
"previous_period"
],
"description": "Set to previous_period to include the received-message count for the immediately preceding window of equal length. The response also includes the change between the two, so you can show '+X% vs last period' without a second request."
},
"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."
}
}
}