// AI Platform Drift

MCP tool-call analytics default changed from all statuses to success only

Cloudflare developer changelog · published 2026-10-31 05:43 UTC
ACTION NEEDED MIGRATE APILIMITS
WHAT CHANGEDCloudflare's MCP tool-call analytics timeseries endpoints now default to response_status=success, counting only successful calls. Previously, counts included all statuses (success, error, and cached). A new response_status query parameter accepts success, error, cached, or all. Invalid or empty values return 400.
WHY IT MATTERSExisting integrations querying these endpoints without an explicit response_status parameter will see lower counts, as failed and cached calls are now excluded from the default response. Historical comparisons will break unless the parameter is added.
WHAT TO DOAdd response_status=all to existing queries against /accounts/{account_id}/access/ai-controls/mcp/analytics/tool-calls/timeseries and related portal and server endpoints to restore previous behavior. Update dashboards and alerts that depend on these counts.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Access, Cloudflare One - Filter MCP tool-call analytics by response status
+https://developers.cloudflare.com/changelog/post/2026-10-28-mcp-analytics-response-status/
+Wed, 28 Oct 2026 00:00:00 GMT
+
+MCP tool-call analytics support a response_status query parameter on the account, portal, and server timeseries endpoints. Use success, error, or cached to count one status, or all to include every status.
+The default is success. Previously, counts included failed and cached calls. If you need the previous all-status counts, set response_status=all explicitly:
+GET /accounts/{account_id}/access/ai-controls/mcp/analytics/tool-calls/timeseries?response_status=all
+The response includes the selected response_status. Invalid values, including an empty value, return 400.
+For all query parameters and scoped endpoints, refer to View tool-call analytics.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningDefault query parameter behavior changed; existing code will return different results without explicit migration.
signalsnew query parameter introduced (response_status) · breaking change: default behavior changed from 'all' to 'success' · existing integrations will see different counts without explicit parameter · migration path documented (response_status=all restores old behavior) · API endpoint behavior change affecting analytics consumers
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)