List Cloudflare zones or export one in BIND format for backup, migration, or DNS configuration review.
Zones for the Cloudflare account (action=list), or one zone exported in BIND format (action=export).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| limit | No | ||
| action | No | list | |
| zone_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| zones | No | ||
| action | Yes | ||
| export | No | ||
| zone_id | No | ||
| has_more | No |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is a safe read-only, non-open-world operation. The description adds useful modality context by noting BIND export formatting, but it omits details such as pagination behavior or what data the export contains, even though an output schema exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single compact sentence with no wasted wording. The action-oriented structure is front-loaded and immediately useful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple and has an output schema plus annotations, so the description does not need to explain return values. Still, with 0% schema description coverage, it should at least clarify pagination parameters and the zone_id requirement for export.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must carry parameter meaning. It explains the action values and implies zone_id for export, but page, limit, and the explicit role of zone_id remain undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource (Cloudflare DNS zones) and the two modes (list zones or export one zone in BIND format). It does not explicitly distinguish this tool from sibling tools such as dns_records, which prevents a top score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The action values imply when to use list versus export, giving some practical guidance. However, it does not state that export requires a zone_id, nor does it compare this tool with relevant alternatives such as dns_records.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.