Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cloudflare: Delete workers script

cloudflare_delete_workers_script
Destructive

Deletes a Cloudflare Workers script and immediately stops its routes; use it to remove obsolete or compromised scripts. Requires Workers Scripts Edit permission.

Instructions

[UNIFIED] Delete a Workers script (requires Workers Scripts Edit permission). DESTRUCTIVE — the script and its routes stop working immediately.

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": {
      "site": "<site>",
      "script_name": "<script_name>"
    },
    "name": "cloudflare_delete_workers_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
account_idNo
script_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds real value on top: the required permission scope and the fact that the script's routes stop working immediately, which is not encoded in the annotations or schema.

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 short sentences, front-loaded with the action and immediately followed by the destructive warning; nothing is redundant.

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 destructive consequence and permission requirement are covered, and no output schema exists, but for a tool whose schema is entirely undocumented the description leaves the account_id/site relationship unresolved — the one ambiguity an agent is most likely to trip on.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters, yet the description explains none of them. It does not clarify what "site" means versus "account_id", nor when the optional account_id should be supplied instead of deriving the account from the site.

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?

States a specific verb and resource ("Delete a Workers script") plus the immediate consequence, which cleanly separates it from the get/list Workers script siblings without needing to name 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?

Gives a prerequisite (Workers Scripts Edit permission) and a strong warning, which implies when the tool should be used, but offers no explicit guidance on alternatives such as fetching the script first or checking routes before deletion.

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