Skip to main content
Glama
Sign In
cloudflare-mcp

cloudflare-mcp

by habib-alqalam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cf_purge_cache

Purge cached content for a Cloudflare zone. Remove all files when everything is true and confirmed, or delete specific URLs by passing files array.

Instructions

Purge cache for a zone. {everything:true} gated by confirm; or files:[urls].

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": "<zone>"
    },
    "name": "cf_purge_cache"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneYes
filesNo
confirmNo
everythingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/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. It partially discloses the safety mechanism by noting {everything:true} is gated by confirm, which is useful context about a required guardrail for a destructive operation. However, it does not state that purge is destructive/irreversible, what requires authentication, or how partial (files) purges behave.

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?

Two terse fragments with zero waste, front-loading the core purpose and then the mode options. The telegraphic style is efficient but slightly under-structured, reading almost like schema shorthand rather than a description.

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?

For a destructive, 4-param tool with zero annotations and no output schema, the description should disclose more: that purging is irreversible, which parameters require confirmation, and how the two modes interact. The mention of the confirm gate helps but is insufficient for the operation's risk profile.

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 0%, so description must compensate. It explains the relationship between the everything and confirm parameters (everything:true requires confirm) and shows the files array with [urls] syntax, which adds meaning beyond the bare schema. But zone and confirm lack standalone semantics, leaving the coverage gap only partially filled.

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 (purge) and resource (cache) with a scope constraint (for a zone), immediately distinguishing it from DNS siblings like cf_dns_create or cf_list_zones. The purpose is clear, though the fragmentary phrasing is terse rather than fully self-explanatory.

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?

The description implies two modes (everything vs files) but gives no guidance on when to use purge-cache versus other cache operations, no prerequisites, and no warning about the destructiveness of the operation. There is no mention of alternatives or exclusions.

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

Deploy Server

Other Tools