Skip to main content
Glama
Cloudflare Workers MCP Server

Cloudflare Workers MCP Server

Update Worker Settings

update_worker_settings
DestructiveIdempotent

Modify a Worker's bindings, compatibility date/flags, logpush, and observability without re-uploading code. Binding changes replace the full set and deploy a new version when no rollout is pending.

Instructions

Update a Worker's settings (bindings, compatibility date/flags, logpush, observability) without re-uploading its code. Bindings REPLACE the Worker's full binding set, except that existing secrets are kept unless listed. Binding and compatibility changes deploy a new version; refuses while a staged version or a gradual rollout is pending.

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

Input Schema

NameRequiredDescriptionDefault
logpushNo
bindingsNoResource bindings — REPLACES the Worker's full binding set
script_nameYesThe name of the Worker script
observabilityNoWorkers Logs configuration
compatibility_dateNoYYYY-MM-DD
compatibility_flagsNoRuntime compatibility flags. nodejs_compat is on by default for compatibility_date >= 2026-08-04, so it is not needed with the default (today) date

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / compatibility_flags / description
      Added value: +"Runtime compatibility flags. nodejs_compat is on by default for compatibility_date >= 2026-08-04, so it is not needed with the default (today) date"
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructive/idempotent but the description carries the real behavioral burden: bindings REPLACE the entire binding set (sharpening what 'destructive' actually destroys), existing secrets survive unless listed, and binding/compatibility edits deploy a new version. These are non-obvious side effects an agent cannot derive from 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?

Three sentences, front-loaded with purpose, then the most dangerous semantic (replacement), then preconditions. Every clause conveys a distinct constraint; nothing is redundant with the title.

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?

For a six-parameter mutation with nested binding objects and no output schema, the description supplies the critical destructive semantics and the refusal preconditions. It stops short of saying what is returned (e.g., a new version id) or confirming that omitted settings are left untouched, which matters given no output schema.

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

Parameters4/5

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

Schema coverage is 83%, so the baseline would be 3, but the description adds replace-vs-merge semantics for `bindings` and the secret-preservation exception that the schema text alone does not convey. It leaves the partial-update behavior of omitted optional fields (logpush, observability) unstated.

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 (update a Worker's settings) and enumerates the exact settings surfaces covered: bindings, compatibility date/flags, logpush, observability. The clause 'without re-uploading its code' cleanly separates it from deploy_worker and create_version in the sibling list.

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?

Gives a clear when-not condition ('refuses while a staged version or a gradual rollout is pending') and implicitly routes code changes to a deploy tool via 'without re-uploading its code'. It never names a sibling tool explicitly, so the alternative routing is inferred rather than stated.

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