cloudflare-mcp-pro

create_worker_route

Map a URL pattern to a Worker script in your Cloudflare zone. Preview without approval; execute only with human confirmation.

Instructions

Create a Worker route mapping a URL pattern to a Worker script. 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>",
      "pattern": "<pattern>"
    },
    "name": "create_worker_route"
  }
}

Input Schema

Name	Required	Description
`zone_id`	Yes	The Cloudflare zone ID (32-char hex). Get it from list_zones.
`pattern`	Yes	Route pattern, e.g. example.com/api/*.
`script`	No	Worker script name to run on this route. Omit to disable on the pattern.
`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.2/5.0

Behavior4/5

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

Annotations indicate non-readOnly and non-destructive, and the description adds the crucial behavior of requiring human approval for mutation and providing a preview without it. This adds value 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?

Two efficient sentences: first defines the purpose, second explains the critical confirm behavior. No redundancy or unnecessary 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 the absence of output schema, the description explains the preview behavior. It covers the core functionality and the confirm gate. Minor gap: does not describe the format of the preview response or explicitly states this is for Cloudflare, though inferred from zone_id.

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?

Input schema covers all 4 parameters with detailed descriptions (100% coverage). The tool description adds no additional parameter information, so the baseline of 3 applies.

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 clearly states the action ('Create'), the resource ('Worker route'), and the function ('mapping a URL pattern to a Worker script'). It distinctly identifies the tool among siblings like create_dns_record or create_queue.

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?

It explicitly states the confirm:true requirement for actual creation and the preview behavior otherwise, giving clear context. However, it does not mention when not to use this tool or compare to alternatives like create_page_rule.

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

Deploy Server