mcp-cloudflare-crunchtools

Delete Page Rule Tool

delete_page_rule_tool

Delete a Cloudflare page rule by zone ID and rule ID to remove outdated redirects, forwarding, or caching behavior from a zone.

Instructions

Delete a 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": "delete_page_rule_tool"
  }
}

Input Schema

Name	Required	Description	Default
`rule_id`	Yes	Page rule ID (32-character hex string)
`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.

Changed3 schema fields changedv0.7.2Oct 12, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / rule_id / description
```
Added value: +"Page rule ID (32-character hex string)"
```
- addedInput schema / properties / zone_id / description
```
Added value: +"Zone ID (32-character hex string)"
```
Changed3 schema fields changedv0.5.1Oct 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / rule_id / description
```
Removed value: -"Page rule ID (32-character hex string)"
```
- 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?

No annotations are provided, so the description carries the full behavioral burden for a destructive operation, and it discloses nothing: no irreversibility warning, no permission/scope requirements, no indication of what happens to dependent resources. The only implicit signal is that 'Delete' mutates state.

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

Conciseness3/5

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

A single four-word sentence with zero waste and the verb front-loaded, so it is structurally clean. But the extreme brevity reflects under-specification rather than efficient communication, so it cannot score higher.

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 mechanical aspects are covered externally: both required parameters are fully described in the schema and an output schema exists, so return values and inputs need no explanation here. What remains missing is any when-to-use or destructive-operation context, which is a real but modest gap given how simple the call is.

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% – both zone_id and rule_id are documented as 32-character hex strings in the schema – and the description adds no further format or constraint detail. Baseline 3 applies when the schema does all the work.

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 (Delete) and resource (page rule), which cleanly separates it from the create/update/list page-rule siblings. It does not, however, add any scope detail beyond what the tool name already conveys (e.g. whether the whole rule or a subset is removed).

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?

No guidance on when to use this versus update_page_rule_tool or list_page_rules_tool, no prerequisites, and no note that the operation is irreversible. The only usage signal is the verb 'Delete' implied by the name.

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

Deploy Server