Skip to main content
Glama
Sign In
mcp-server-cloudflare

mcp-server-cloudflare

by ofershap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cf_cache_purge

Purge Cloudflare cache for specific URLs or entire zones to ensure content updates are immediately visible.

Instructions

Purge Cloudflare cache (all or specific 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": {
      "zoneId": "<zoneId>"
    },
    "name": "cf_cache_purge"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneIdYesZone ID
purgeAllNoPurge everything (use with caution)
urlsNoSpecific URLs to purge

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/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 full burden. It mentions 'all or specific URLs' but lacks critical behavioral details like required permissions, rate limits, side effects (e.g., temporary performance impact), or response format. The 'use with caution' warning is in the schema, not the description.

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 a single, efficient sentence that front-loads the core action ('Purge Cloudflare cache') and specifies scope ('all or specific URLs') without unnecessary words. Every part earns its place.

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?

Given no annotations, no output schema, and a mutation tool with potential side effects, the description is inadequate. It lacks details on permissions, consequences, error handling, or return values, leaving significant gaps for an AI agent to use it safely and effectively.

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%, so the schema fully documents parameters. The description adds minimal value by hinting at 'all or specific URLs', which aligns with purgeAll and urls parameters but doesn't provide additional syntax or format details beyond the schema.

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 clearly states the verb ('Purge') and resource ('Cloudflare cache'), specifying it can target 'all or specific URLs'. It distinguishes from siblings like DNS or KV tools by focusing on cache operations, though it doesn't explicitly contrast with them.

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

Usage Guidelines3/5

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

The description implies usage for cache purging but provides no explicit guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It mentions 'use with caution' in the schema but not in the description itself.

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