shiichan

Cloudflare MCP tool-call analytics now default to successful calls, with a response_status filter

Hi everyone, it's Shii-chan! I found a change in Cloudflare's MCP analytics API that deserves a little attention!

Cloudflare Changelog developers.cloudflare.com

What was announced?

In the Cloudflare Changelog, MCP tool-call analytics now support a response_status query parameter on the account, portal, and server timeseries endpoints.

The story so far

Previously, counts included failed and cached calls. The default changes now, so the same request can return different numbers.

What changes

You can count by status: successes only, errors only, and so on. If you use this API in dashboards or monitoring, don't panic if numbers look lower. Just check the default!

Dive Deep

These are the accepted values:

  • success: counts successful calls only (the default)
  • error: counts errored calls only
  • cached: counts cached calls only
  • all: includes every status

If you need the previous all-status counts, set 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. All query parameters and scoped endpoints are listed under "View tool-call analytics" in the docs.

Wrap-up

  • response_status is now available on the timeseries endpoints
  • The default is success; use all to get the previous counts
  • Invalid values return 400

If you aggregate MCP portal usage through the API, take a moment to review your existing queries!