List alert triggers
alerts.history.list
Lists the times alerts triggered, newest first, paginated by cursor (limit 50 by default, up to 200): the alert (alert_id, alert_name), the watched organization and platform account, the metric, current_value and previous_value with delta_absolute and delta_percent, the threshold and condition, the severity (info, warning or critical, by how far the change went past the threshold), the evaluated date ranges and the addresses the email went to (recipient_emails, email_sent). Filter by alert_id or by target_org_id (both: a filtered page is filled by reading further, up to 600 triggers per call). Entries of deleted alerts stay. Only the hourly evaluation writes here; reading sends nothing. With Google Ads, Google Business Profile, LinkedIn, TikTok or YouTube, their terms limit it through the API and the MCP: what they do not allow answers 403 platform_terms_restricted, and their records are left out of the response (the permissions guide lists what each platform allows).
- Alcance
alerts:read- Permiso
- Ver el módulo
- Tool del MCP
alerts_history_listEn la superficie completa; en la compacta,mb_execute_operationconid: "alerts.history.list".
Costo declarado: hasta 601 lecturas y 0 escrituras por llamada (cuentan en el cupo diario).
Parámetros
limitintegerqueryopcionalHow many per page (default 50, at most 200).
Por defecto: 50
cursorstringqueryopcionalThe next_cursor of the previous page.
alert_idstringqueryopcionalOnly the triggers of this alert.
target_org_idstringqueryopcionalOnly the triggers of alerts that watch this organization.
Respuesta
dataarray<object>has_morebooleannext_cursorstringErrores
Ejemplo
curl "https://api.mb-suite.com/v1/alerts/history" \
-H "Authorization: Bearer $MB_API_KEY"Probar con tu API key de prueba
Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.
curl "https://api.mb-suite.com/v1/alerts/history" \
-H "Authorization: Bearer $MB_TEST_KEY"