Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cloudflare: List workers scripts

cloudflare_list_workers_scripts
Read-only

List Cloudflare Workers scripts in your account to retrieve script names, modification dates, and sizes. Use it to inventory deployed Workers and track recent changes.

Instructions

[UNIFIED] List Workers scripts in the account (requires Workers Scripts permission and Account ID). Returns script names, modification dates and sizes.

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>"
    },
    "name": "cloudflare_list_workers_scripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description's main added value is the permission requirement and the shape of the returned fields (names, modification dates, sizes). It does not mention pagination, result limits, or behavior on an empty account, which matters for a list endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the action and scope front-loaded. The '[UNIFIED]' prefix and parenthetical prerequisite add noise but do not obscure the core statement.

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?

With no output schema, describing the returned fields is helpful, and the permission note covers auth. However, the required 'site' parameter, pagination, and result-size behavior are all left unexplained, leaving real gaps for a two-parameter list tool.

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 2 parameters, so the description must carry the meaning itself. It only gestures at account_id ('requires... Account ID' — which is arguably at odds with the schema marking account_id optional with a null default) and says nothing at all about the required 'site' parameter.

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 gives a specific verb and resource ('List Workers scripts') plus the scope ('in the account'), which cleanly separates it from the get/delete Workers script siblings. It does not explicitly name an alternative, but the list/get/delete contrast is unambiguous from the verb alone.

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?

It states prerequisites (Workers Scripts permission, Account ID), which tells the agent when the call can succeed, but it offers no explicit guidance on when to choose this over cloudflare_get_workers_script or other list tools. Usage is implied by the 'list all scripts' framing rather than stated.

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