Skip to main content
Glama
Cloudflare Workers MCP Server

Cloudflare Workers MCP Server

List Versions

list_versions
Read-onlyIdempotent

Retrieves a Worker's 100 most recent versions with ID, number, author, source, and deploy message/tag, so you can inspect immutable snapshots and identify which are live.

Instructions

List a Worker's 100 most recent versions (newest first): version ID, number, author, source, and deploy message/tag. Versions are immutable snapshots; use list_deployments to see which are live.

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_versions"
  }
}

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral facts: results are capped at the 100 most recent, returned newest-first, and versions are immutable snapshots — the last point being important context that explains why there is no update_version sibling to reach for.

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 sentences, both dense with non-redundant information: the first front-loads scope, ordering, cap, and returned fields; the second supplies the immutability caveat and the sibling hand-off. Nothing is padded or repeated from 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?

With no output schema, the description usefully enumerates the returned fields, and for a single-parameter read tool that is close to sufficient. The remaining minor gap is behavior when script_name does not resolve (empty list vs. error), which an agent might want to know.

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% for the single script_name parameter, so the schema already carries the semantics and the baseline applies. The description's phrase "a Worker's" reinforces the scoping but adds no format, naming, or lookup detail beyond the schema.

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 ("List a Worker's ... versions") plus the exact scope: 100 most recent, newest first. The returned fields (version ID, number, author, source, deploy message/tag) further pin down what the tool yields, so an agent can distinguish it from get_version and create_version without opening any schema.

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?

Explicitly routes the agent to list_deployments "to see which are live", a clear when-to-use-this-instead signal for the most likely confusion in this sibling cluster. It stops short of covering the other near neighbor, get_version, for retrieving a single version by ID, but the usage context is otherwise clear.

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