mcp-cloudflare-crunchtools

get_zone_analytics_tool

Retrieve Cloudflare zone traffic analytics summaries—requests, unique visitors, bandwidth, cache ratio, and status code breakdown—for a chosen date range by zone ID or domain.

Instructions

Get zone traffic analytics summary.

Returns total requests, unique visitors, bandwidth, cache ratio, and status code breakdown for the given date range.

Provide either zone_id or zone_name, not both.

Args: zone_id: Zone ID (32-character hex string) zone_name: Zone name (domain like example.com) since: Start date ISO format (default: 30 days ago) until: End date ISO format (default: today)

Returns: Analytics summary with requests, bandwidth, visitors, and status codes

Input Schema

TableJSON Schema

Name	Required	Description	Default
`since`	No
`until`	No
`zone_id`	No
`zone_name`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.5.1Oct 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / since / description
```
Removed value: -"Start date ISO format (default: 30 days ago)"
```
- removedInput schema / properties / until / description
```
Removed value: -"End date ISO format (default: today)"
```
- removedInput schema / properties / zone_id / description
```
Removed value: -"Zone ID (32-character hex string)"
```
- removedInput schema / properties / zone_name / description
```
Removed value: -"Zone name (domain like example.com)"
```
First observedv0.5.0Aug 19, 2026

TDQS

A4.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It usefully discloses the default date range behavior (30 days ago / today), which an agent needs to know, but never states that this is a read-only, non-mutating operation, nor any auth or rate-limit characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and efficiently structured with Args/Returns sections. The final 'Returns:' block largely restates the opening paragraph, which is mild redundancy rather than harmful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, the description need not explain return shape, yet it still lists metrics, and it covers all parameters and defaults. The only real gap is the absence of any read-only/side-effect statement to substitute for missing annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does: it documents all four parameters with formats (32-character hex string, domain like example.com, ISO date format) and default values, plus the either/or constraint that the schema does not express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get zone traffic analytics summary') and enumerates the exact metrics returned (requests, visitors, bandwidth, cache ratio, status codes). This clearly separates it from analytics siblings like get_top_pages_tool and get_traffic_by_country_tool, which cover different dimensions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the mutual-exclusivity rule ('either zone_id or zone_name, not both') and documents the default date window. It gives clear context for calling the tool but does not name when to prefer alternative analytics siblings or state exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.