mcp-cloudflare-crunchtools

Get Top Pages Tool

get_top_pages_tool

Read-only

Retrieve top pages by request count for a Cloudflare zone using a zone ID or domain, with optional date range and result limit. Use it to analyze traffic trends.

Instructions

Get top pages by request count.

Provide either zone_id or zone_name, not both.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_top_pages_tool"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of results (default: 15)
`since`	No	Start date ISO format (default: 30 days ago)
`until`	No	End date ISO format (default: today)
`zone_id`	No	Zone ID (32-character hex string)
`zone_name`	No	Zone name (domain like example.com)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.7.2Oct 12, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / limit / description
```
Added value: +"Number of results (default: 15)"
```
- addedInput schema / properties / since / description
```
Added value: +"Start date ISO format (default: 30 days ago)"
```
- addedInput schema / properties / until / description
```
Added value: +"End date ISO format (default: today)"
```
- addedInput schema / properties / zone_id / description
```
Added value: +"Zone ID (32-character hex string)"
```
- addedInput schema / properties / zone_name / description
```
Added value: +"Zone name (domain like example.com)"
```
Changed6 schema fields changedv0.5.1Oct 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / limit / description
```
Removed value: -"Number of results (default: 15)"
```
- 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

B3.4/5.0

Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description carries a lower burden, but it adds nothing behavioral: no note on rate limits, pagination, result ordering, or how ties are broken. Nothing here goes beyond the annotation and the schema.

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

Conciseness5/5

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

Two short sentences, front-loaded with the resource and metric, followed immediately by the one constraint that matters. No filler or restatement of the title.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and defaults for limit/since/until are in the schema. However, with zero required parameters the description never says what happens if neither zone_id nor zone_name is supplied, leaving a real ambiguity about the tool's behavior.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds the mutual-exclusivity rule between zone_id and zone_name, which the schema does not encode (both are independently nullable). That is genuine added meaning for two of the five parameters.

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

Purpose4/5

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

States a specific verb (Get), resource (top pages), and ranking metric (request count), which clearly separates it from generic analytics siblings like get_zone_analytics_tool. It does not explicitly name or contrast with those siblings, so it falls just short of 5.

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

Usage Guidelines3/5

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

The only guidance is the exclusivity constraint 'Provide either zone_id or zone_name, not both,' which is about parameter usage rather than when to pick this tool over get_zone_analytics_tool or get_traffic_by_country_tool. Usage is implied by the name and metric, not stated.

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

Deploy Server