mcp-cloudflare-crunchtools

Update Page Rule Tool

update_page_rule_tool

Update an existing Cloudflare page rule using its zone and rule IDs, changing URL targets, actions, priority, or status.

Instructions

Update an existing page rule.

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>",
      "rule_id": "<rule_id>"
    },
    "name": "update_page_rule_tool"
  }
}

Input Schema

Name	Required	Description
`status`	No	Status (optional)
`actions`	No	Actions (optional)
`rule_id`	Yes	Page rule ID (32-character hex string)
`targets`	No	URL patterns (optional)
`zone_id`	Yes	Zone ID (32-character hex string)
`priority`	No	Priority (optional)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.7.2Oct 12, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / actions / description
```
Added value: +"Actions (optional)"
```
- addedInput schema / properties / priority / description
```
Added value: +"Priority (optional)"
```
- addedInput schema / properties / rule_id / description
```
Added value: +"Page rule ID (32-character hex string)"
```
- addedInput schema / properties / status / description
```
Added value: +"Status (optional)"
```
- addedInput schema / properties / targets / description
```
Added value: +"URL patterns (optional)"
```
- addedInput schema / properties / zone_id / description
```
Added value: +"Zone ID (32-character hex string)"
```
Changed7 schema fields changedv0.5.1Oct 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / actions / description
```
Removed value: -"Actions (optional)"
```
- removedInput schema / properties / priority / description
```
Removed value: -"Priority (optional)"
```
- removedInput schema / properties / rule_id / description
```
Removed value: -"Page rule ID (32-character hex string)"
```
- removedInput schema / properties / status / description
```
Removed value: -"Status (optional)"
```
- removedInput schema / properties / targets / description
```
Removed value: -"URL patterns (optional)"
```
- removedInput schema / properties / zone_id / description
```
Removed value: -"Zone ID (32-character hex string)"
```
First observedv0.5.0Aug 19, 2026

TDQS

C2.7/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden and discloses nothing: not what happens to fields omitted from the update, not whether the operation requires specific permissions, not whether changes are reversible. For a mutation tool with zero annotation coverage this is a serious gap.

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 front-loaded sentence with zero padding, so it is not verbose. It is, however, thin rather than efficiently dense — the brevity reflects under-specification rather than crisp information packing.

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

Completeness2/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 not be explained, and the schema is fully documented. But this is a 6-parameter mutation tool with no annotations and no guidance on partial-update semantics or required versus optional behavior, leaving the agent without enough context to invoke it confidently.

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%, and each parameter (zone_id, rule_id, status, actions, targets, priority) is documented in the schema itself. The description adds nothing beyond the schema, 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?

The description states a specific verb (Update) and resource (page rule), so the agent knows exactly what kind of operation this is. However, it does nothing to distinguish itself from its obvious siblings (create_page_rule_tool, delete_page_rule_tool, list_page_rules_tool) or the parallel update_waf_rule_tool, so it stops short of a 5.

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 guidance on when to use this tool versus create/delete/list page rules, no prerequisites, and no conditions that select it over alternatives. The word 'existing' faintly implies the rule must already exist, but no actual usage guidance is given.

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

Deploy Server