mcp-cloudflare-crunchtools

List Page Rules Tool

list_page_rules_tool

Read-only

Retrieve all page rules for a Cloudflare zone, optionally filtered by status or sorted, to inspect and manage zone-level configurations.

Instructions

List all page rules for a zone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "zone_id": "<zone_id>"
    },
    "name": "list_page_rules_tool"
  }
}

Input Schema

Name	Required	Description	Default
`order`	No	Sort order (status, priority)	priority
`status`	No	Filter by status (active, disabled)
`zone_id`	Yes	Zone ID (32-character hex string)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.7.2Oct 12, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / order / description
```
Added value: +"Sort order (status, priority)"
```
- addedInput schema / properties / status / description
```
Added value: +"Filter by status (active, disabled)"
```
- addedInput schema / properties / zone_id / description
```
Added value: +"Zone ID (32-character hex string)"
```
Changed4 schema fields changedv0.5.1Oct 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / order / description
```
Removed value: -"Sort order (status, priority)"
```
- removedInput schema / properties / status / description
```
Removed value: -"Filter by status (active, disabled)"
```
- removedInput schema / properties / zone_id / description
```
Removed value: -"Zone ID (32-character hex string)"
```
First observedv0.5.0Aug 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered structurally. Beyond that, the description adds nothing behavioral — no pagination, no result-volume or ordering caveats, no note that filters are optional. It simply restates the operation.

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?

A single short sentence with zero padding and the resource front-loaded. It is efficient, though the brevity edges toward under-specification rather than true conciseness.

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?

With an output schema present and annotations covering the read-only nature, the description does not need to explain return values or safety. But for a list tool with filtering and sort parameters, it omits any hint about result shape, pagination, or how filters interact, leaving it minimally adequate.

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

Parameters3/5

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

Schema description coverage is 100%: zone_id, order (with accepted values), and status are all documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 and resource: 'List all page rules for a zone.' An agent can immediately tell this is a read/list operation over page rules. However, it does nothing to distinguish itself from the many other list_* rules tools in the sibling set (header rules, URL rewrite rules), relying on the name alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as create_page_rule_tool or update_page_rule_tool. The agent must infer from the name that this is the retrieval counterpart to those mutation tools.

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

Deploy Server