Skip to main content
Glama
Cloudflare Workers MCP Server

Cloudflare Workers MCP Server

List Deployments

list_deployments
Read-onlyIdempotent

Retrieve a Worker's deployments newest first, showing traffic percentages across versions and identifying the live deployment by its newest timestamp.

Instructions

List a Worker's deployments (newest first). Each deployment maps traffic percentages to one or more versions; the newest deployment is the live one.

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": "list_deployments"
  }
}

Input Schema

NameRequiredDescriptionDefault
script_nameYesThe name of the Worker script

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description goes beyond that by disclosing result ordering (newest first) and the domain semantics — each deployment maps traffic percentages to versions and the newest is live — which materially helps an agent interpret output. It omits any mention of pagination or result bounds despite openWorldHint=true.

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 tight sentences with the action front-loaded and zero redundant wording. Every clause (ordering, traffic mapping, live-ness) carries information an agent would otherwise have to guess.

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 single-parameter read tool with no output schema, the description covers what is returned conceptually and how to interpret it. The main remaining gap is volume/pagination behavior, minor given the tool's simplicity and read-only annotations.

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?

Only one parameter (script_name) at 100% schema coverage, so the schema fully documents it. The description adds no extra meaning such as name formatting or whether a worker ID is accepted, which is the expected baseline for fully-covered schemas.

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 (list) and resource (a Worker's deployments) plus the ordering guarantee 'newest first'. It does not distinguish itself from adjacent siblings such as list_versions or list_previews, so an agent must infer which listing it needs.

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?

Usage is only implied by the verb 'list' — there is no explicit statement of when to prefer this over list_versions or list_previews, nor of prerequisites (e.g., that the Worker must exist). The note that the newest deployment is the live one gives some context for interpreting results but not for tool selection.

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