Metrics · Alerts · API reference

GET/v1/alerts/metrics

List the metrics an alert can watch

alerts.metrics.list

ReadIdempotentSince 2026-11-01

With platform: the metrics an alert can watch on that platform (id, label, format currency/number/percent, and higher_is_better: false when going up is bad, like CPC or bounce rate) and its recommended templates (template id, metric, operator, threshold, threshold_type, period, category and a short description in Spanish). Without platform: every platform with how many metrics and templates it has (metric_count, template_count), so ask again with platform for the detail. It is the product's static catalog: no reads and no calls to the platforms. Use a metric id here as metric in alerts.alerts.create (and a template id as template_id).

Scope: alerts:read
Permission: View the module
MCP tool: alerts_metrics_listOn the full surface; on the compact one, mb_execute_operation with id: "alerts.metrics.list".

Declared cost: up to 0 reads and 0 writes per call (they count against the daily quota).

Parameters

platformenumqueryoptional

The platform whose metrics and templates to list. Without it, only the platforms with how many metrics and templates each has (B6-42: the whole catalog was about 50 thousand characters).

Values: google_ads, meta_ads, tiktok_ads, tiktok, linkedin_ads, linkedin_page, google_analytics, google_search_console, google_business_profile, facebook_page, instagram, youtube

Response

dataarray<object>

One item per platform (only the asked platform with platform).

Errors

invalid_input unknown_field authentication_required scope_insufficient module_access_denied operation_not_found rate_limited quota_exceeded

Example

curl "https://api.mb-suite.com/v1/alerts/metrics" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/alerts/metrics" \
  -H "Authorization: Bearer $MB_TEST_KEY"