Skip to main content
Glama
jeffgolden

Cloudflare MCP Server

by jeffgolden

cloudflare-dns-mcp_list_zone_settings

Retrieve and manage DNS, security, and redirect settings for a specified zone on Cloudflare. Streamlines configuration and monitoring tasks for AI-assisted automation.

Instructions

Retrieve all settings for a specific zone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_nameYes

Implementation Reference

  • The core handler function for the tool. It validates the input zone_name, queries Cloudflare zones API to get zone ID, then fetches and returns the zone settings from /zones/{zoneId}/settings endpoint.
      const { zone_name } = ListZoneSettingsInputSchema.parse(params);
      const zones = await client.get<Array<{ id: string; name: string }>>('/zones', { name: zone_name });
      if (zones.length === 0) throw new Error(`Zone ${zone_name} not found`);
      const settings = await client.get<any>(`/zones/${zones[0].id}/settings`);
      return settings;
    },
  • Zod input schema definition requiring a 'zone_name' string parameter. The inputSchema and outputSchema are derived from this and set on the tool object.
    const listZoneSettingsTool: Tool = {
  • Local registration of the tool object within the 'tools' record returned by getDnsTools(client) function.
    'cloudflare-dns-mcp/list_zone_settings': listZoneSettingsTool,
  • src/index.ts:25-31 (registration)
    Aggregation of all tools objects, including dnsTools.tools (which contains the list_zone_settings tool), into a single allTools map used by the MCP server.
    const allTools = {
      ...dnsTools.tools,
      ...securityTools.tools,
      ...sslCertTools.tools,
      ...echoTools.tools,
      ...redirectTools.tools,
      ...zoneTools.tools,
  • Helper code that sanitizes tool names by replacing non-alphanumeric chars (like '/') with '_', transforming 'cloudflare-dns-mcp/list_zone_settings' to 'cloudflare-dns-mcp_list_zone_settings' for client use.
    const toolsMap: Record<string, any> = {};
    for (const tool of Object.values(allTools)) {
      const safeName = tool.name.replace(/[^a-zA-Z0-9_-]/g, '_');
      toolsMap[safeName] = tool;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Retrieve' implies a read-only operation, the description doesn't specify whether this requires authentication, what format the settings are returned in, if there are rate limits, or if it's paginated. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence that gets straight to the point with no wasted words. It's appropriately sized for a simple retrieval tool and front-loads the core purpose effectively.

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?

Given the lack of annotations and output schema, the description is insufficiently complete. It doesn't explain what 'settings' include, how they're returned, or address the ambiguity with the sibling 'get_zone_settings' tool. For a tool that likely returns complex configuration data, more context is needed to help the agent use it correctly.

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

Parameters3/5

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

The description mentions 'a specific zone' which aligns with the single parameter 'zone_name', but doesn't add any meaning beyond what the schema already indicates. With 0% schema description coverage, the parameter is undocumented in both the schema and description. The description doesn't compensate for this gap by explaining what 'zone_name' represents or its expected format, so it meets the baseline for minimal value.

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?

The description clearly states the verb ('Retrieve') and resource ('all settings for a specific zone'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from the sibling tool 'cloudflare-dns-mcp_get_zone_settings', which appears to have a similar function, leaving some ambiguity about when to use one versus the other.

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?

The description provides no guidance on when to use this tool versus alternatives. With a sibling tool named 'cloudflare-dns-mcp_get_zone_settings' that seems related, the agent is left without any indication of the differences or appropriate contexts for each tool, which could lead to incorrect tool selection.

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

Related 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/jeffgolden/cloudflare_mcp'

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