cloudflare-mcp

cf_dns_list

Retrieve DNS records for a Cloudflare zone by domain name or zone ID, with optional filtering by record name and type.

Instructions

List DNS records for a zone (zone = domain name or zone id).

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": {
      "zone": "<zone>"
    },
    "name": "cf_dns_list"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`type`	No
`zone`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 2, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations provided, so the description carries full burden. It says it lists, implying a read, but doesn't disclose whether it requires authentication, returns paginated results, or has rate limits. Minimal behavioral context.

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

Conciseness5/5

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

A single efficient sentence with the key scoping detail front-loaded in parentheses. No waste.

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

Completeness2/5

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

With no annotations, no output schema, and 0% schema coverage, the description is too thin. It should explain what the name/type params do and what the tool returns to be complete.

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%, so no parameter documentation exists. The description only clarifies the 'zone' parameter (domain name or zone id) but says nothing about 'name' or 'type' filters, leaving 2 of 3 params undocumented.

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 the specific verb (List) and resource (DNS records) with scoping to a zone. Clearly distinguishes from siblings cf_dns_create/update/delete, though it doesn't explicitly name them.

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

Usage Guidelines2/5

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

No guidance on when to use this vs alternatives or when not to. The parenthetical clarifies the zone param but provides no usage context.

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

Deploy Server