mcp-cloudflare-crunchtools

create_page_rule_tool

Create a new Cloudflare page rule for a zone, specifying URL pattern targets and actions to control caching, security, and performance. Optionally set priority and status.

Instructions

Create a new page rule.

Args: zone_id: Zone ID (32-character hex string) targets: URL pattern targets actions: Page rule actions priority: Rule priority 1-1000 (default: 1) status: active or disabled (default: active)

Returns: Created page rule details

Input Schema

TableJSON Schema

Name	Required	Default
`status`	No	active
`actions`	Yes
`targets`	Yes
`zone_id`	Yes
`priority`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.5.1Oct 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / actions / description
```
Removed value: -"Page rule actions"
```
- removedInput schema / properties / priority / description
```
Removed value: -"Rule priority 1-1000 (default: 1)"
```
- removedInput schema / properties / status / description
```
Removed value: -"active or disabled (default: active)"
```
- removedInput schema / properties / targets / description
```
Removed value: -"URL pattern targets"
```
- removedInput schema / properties / zone_id / description
```
Removed value: -"Zone ID (32-character hex string)"
```
First observedv0.5.0Aug 19, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden, and it discloses little behavior beyond a mutation. It does not mention required permissions, whether creation conflicts with existing matching rules, idempotency, or zone-scoping constraints.

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?

The content is front-loaded with the purpose sentence, then a clean Args/Returns layout with one line per parameter. Every line earns its place, though the Returns section is partly redundant given the output schema.

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?

The presence of an output schema means return values need not be explained, and the Args block covers the 0%-coverage schema reasonably. Still, for an unannotated mutation tool it omits permission requirements, conflict behavior with existing rules, and error/rollback characteristics.

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 description coverage is 0%, so the description must compensate, and it largely does: it documents all five parameters, including the 32-character hex format for zone_id and the semantic role of targets (URL patterns) and actions. The defaults for priority and status duplicate the schema, but the format and meaning details are genuinely additive.

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?

The description states a specific verb and resource ('Create a new page rule'), which cleanly distinguishes it from update_page_rule_tool and delete_page_rule_tool by operation. However, it does not differentiate scope or behavior from siblings like list_page_rules_tool beyond the verb itself.

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. The only implicit usage signal is the verb 'Create', which the name already supplies.

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