NetBird
sms_stats_by_error_code
SMS stats grouped by our normalized failure reason, which answers which reasons are driving your failures. The grouping key is the same value as the `error_code` filter on `sms_list`, so a row joins straight to the messages behind it. Ranked by the `sort` metric (default `failed`) and capped by `limit`.
Remote bird/mcp
Remote (network-hosted)
Other tools also called sms_stats_by_error_code?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"to": {
"type": "string",
"description": "End date (inclusive) in YYYY-MM-DD, interpreted as a calendar day in timezone (a UTC day when timezone is omitted). Defaults to today in that timezone when omitted. Window may not exceed 365 days."
},
"from": {
"type": "string",
"description": "Start date (inclusive) in YYYY-MM-DD, interpreted as a calendar day in timezone (a UTC day when timezone is omitted). Defaults to 30 days before to when omitted; with include_trend=true and trend_grain=hourly the default tightens to keep the window within the 720-hour trend cap."
},
"sort": {
"type": "string",
"examples": [
"accepted",
"sent",
"delivered",
"undelivered",
"failed",
"rejected",
"expired"
],
"description": "Metric to rank rows by, applied descending. Defaults to failed. Only lifecycle counts are sortable; this breakdown has no rates."
},
"limit": {
"type": "integer",
"description": "Maximum number of error-code rows to return, ranked by the sort field 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."
},
"trend_grain": {
"type": "string",
"examples": [
"daily",
"hourly"
],
"description": "Bucket grain for the trend series. Has no effect unless include_trend=true."
},
"include_trend": {
"type": "boolean",
"description": "When true, each row also carries a trend array: a short per-bucket lifecycle-count series for that row over the window. Returned only when limit is 50 or fewer and the window is at most 90 days (trend_grain=daily) or 720 hours (trend_grain=hourly); a larger request returns 422."
}
}
}