Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cloudflare: List zones

cloudflare_list_zones
Read-only

List Cloudflare zones available to your API token, with optional filters for exact zone name or status and pagination. Retrieve zone IDs, names, statuses, name servers, and plans.

Instructions

[UNIFIED] List Cloudflare zones the token can access. Supports filtering by exact zone name and status (active, pending, development, deleted, moved), plus pagination. Returns zone id, name, status, name servers and plan.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
pageNo
siteYes
statusNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds useful context by noting the token-scoped visibility and the exact set of return fields. It stops short on pagination behavior (defaults, limits) and on what 'site' does, leaving some operational behavior undisclosed.

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 front-loaded sentences that describe scope, filters, pagination and returns with little waste. The '[UNIFIED]' tag adds no informational value and slightly clutters the opening.

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?

For a read-only list tool with no output schema, the description usefully enumerates returned fields (id, name, status, name servers, plan) and the valid status values. It remains incomplete on the required 'site' parameter and on pagination semantics, which an agent needs to call it correctly.

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?

With 0% schema coverage the description must carry the parameter meaning, and it does define the name filter, the status filter with its five allowed values, and pagination via page/per_page. However, the required 'site' parameter is never mentioned, which is a meaningful gap for a mandatory argument.

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 and resource ('List Cloudflare zones') and scope ('the token can access'), which lets an agent distinguish it from cloudflare_get_zone for single-zone retrieval. It does not explicitly name a sibling or exclusion, so it falls short of a 5.

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 through filter capabilities ('filtering by exact zone name and status') plus pagination. There is no statement of when to prefer this over cloudflare_get_zone or when listing is the wrong choice.

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