cloudflare-mcp-pro

delete_worker_route

DestructiveIdempotent

Delete a Cloudflare Worker route by its ID. Set confirm:true to execute the deletion; otherwise, a preview is returned.

Instructions

Delete a Worker route by ID. Requires confirm:true (human-approval gate); without it returns a preview only.

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>",
      "route_id": "<route_id>"
    },
    "name": "delete_worker_route"
  }
}

Input Schema

Name	Required	Description
`zone_id`	Yes	The Cloudflare zone ID (32-char hex). Get it from list_zones.
`route_id`	Yes	Route ID (from list_worker_routes).
`confirm`	No	Human-approval gate: must be true to actually perform this mutating operation. Omit or set false to get a non-executing preview of what would happen (with secrets redacted). A human should approve before this is set to true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, aligning with the description's mention of a destructive operation. The description adds detail about the preview behavior when confirm is false, enhancing transparency beyond annotations.

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?

The description is concise with two sentences, front-loading the purpose. Every sentence is informative with no wasted words.

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

Completeness4/5

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

Given no output schema, the description partially covers return behavior (preview vs execution). It explains the confirm gate and parameter sources. Slight gap: does not describe the success response format, but overall sufficient.

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

Parameters5/5

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

Despite high schema coverage, the description adds significant meaning: 'confirm' is explained as a human-approval gate, and references are made to list_zones and list_worker_routes for getting the IDs. This goes beyond the schema.

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

Purpose5/5

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

The description explicitly states 'Delete a Worker route by ID', providing a clear verb and resource. This distinguishes it from sibling tools like delete_worker or delete_dns_record.

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

Usage Guidelines4/5

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

The description clearly explains the confirm parameter as a human-approval gate, indicating when to set it true (for actual deletion) vs false (for preview). It does not explicitly exclude alternatives but provides sufficient context for usage.

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

Deploy Server