Skip to main content
Glama

List Cloudflare domains

list_cloudflare_domains
Read-only

List the Cloudflare-hosted domains (zones) this organisation's connected Cloudflare credential can reach, with each domain's id, status and assigned nameservers. Call this first to resolve a domain name to the domain_id the DNS record tools take - pass 'name' when the user already named the domain, which resolves it in one lookup instead of a walk through every domain in the account. A domain whose status is not 'active' carries a warning: its nameservers are not live at Cloudflare yet, so records written into it will not resolve. If the organisation has connected no Cloudflare credential, this reports that and the user must connect one on the Credentials page. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cloudflare_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoResolve one domain by exact name instead of listing them all. An empty result means Ankra does not reach that domain - either it is not in Cloudflare, or the connected token is scoped away from it.
credential_nameNoWhich connected Cloudflare credential to use. Omit unless the organisation has several; with one connected credential Ankra resolves it automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses the warning semantics for non-'active' status zones (nameservers not live, records won't resolve) and the failure behavior when no Cloudflare credential is connected. It also explains what an empty result implies, which the annotations cannot convey.

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 lead sentence front-loads purpose and return fields, and subsequent sentences cover resolution, warnings, and prerequisites. It is a dense single paragraph, slightly long, but no sentence is filler.

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?

Complete for a read-only list tool with no output schema: it describes return fields, the resolution path for DNS record tools, the degraded-status caveat, and the missing-credential case. An agent has everything needed to call it and interpret results.

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?

Schema coverage is 100%, so the baseline would be 3; the description earns credit by explaining the purpose of 'name' as a single-lookup fast path versus listing everything, adding intent beyond the schema's own text. credential_name is only implicitly covered via the auto-resolution note.

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 the specific verb and resource ('List the Cloudflare-hosted domains (zones)'), names the scope (this organisation's connected credential), and enumerates the returned fields (id, status, nameservers). It is clearly distinguishable from siblings like list_cloudflare_dns_records or create_cloudflare_dns_record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Call this first to resolve a domain name to the domain_id the DNS record tools take' and instructs passing 'name' when the user already named the domain, with a stated efficiency rationale over walking all domains. It also names the prerequisite (connect a credential on the Credentials page) when none exists.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.