Skip to main content
Glama

cf_list_zones

List Cloudflare zones visible to your token, filtered by account or name pattern. Returns zones with key details for SOC investigation.

Instructions

List Cloudflare zones (domains) the token can see.

Args:
    account_id: optional account-ID filter. Defaults to CF_ACCOUNT_ID env
        var when set, otherwise lists across all accessible accounts.
    name_pattern: optional glob filter applied client-side (e.g.
        "*.example.*"). Cloudflare's API does not support glob, so this
        is a post-filter on the API response.
    max_pages: pagination cap (default 5 × per_page 50 = 250 zones).

Calls: GET /zones (auto-paginated).

Returns: envelope with `data = {zones: [...], count, ...}`.

**Compact projection** — each zone is reduced to id, name, status, paused,
type, created_on, modified_on, activated_on, development_mode,
account_id, account_name, plan_name. Full zone config (name_servers,
name_servers_history, owner, permissions, meta, etc.) is dropped to keep
multi-page walks under the 20K-token response ceiling. For full config,
use `cf_get_zone(zone_id)`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNo
name_patternNo
max_pagesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: name_pattern is a client-side post-filter due to API limitations, max_pages default and auto-pagination behavior, and the compact projection that drops fields to avoid token limits. This exceeds what annotations would normally provide.

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?

The description is well-structured with clear sections (Args, Calls, Returns, projection note). It is comprehensive but slightly verbose; still, every sentence adds value. It front-loads the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description still provides essential context: return envelope structure, compact projection rationale, and reference to cf_get_zone for full data. This completes the picture for the agent without over-specifying.

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

Parameters5/5

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

Schema coverage is 0% (no parameter descriptions in schema), but the description entirely compensates. It explains account_id defaults to an env var, name_pattern is a client-side glob, and max_pages is a pagination cap. This adds critical meaning beyond the raw schema types.

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?

The description starts with 'List Cloudflare zones (domains) the token can see.' This is a specific verb and resource, clearly distinguishing it from sibling tools like cf_list_access_apps or cf_list_accounts. The tool's scope is well-defined.

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?

The description explains the purpose of each parameter (account_id filter, name_pattern with glob limitation, max_pages pagination cap) and explicitly directs users to cf_get_zone for full config. However, it does not explicitly state when not to use this tool vs. alternatives, though the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wojtekkura/cf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server