Skip to main content
Glama
jeffgolden

Cloudflare MCP Server

by jeffgolden

cloudflare-dns-mcp_list_ssl_certs

Retrieve a list of SSL certificate packs associated with a specific zone, enabling efficient management and monitoring of certificates within the Cloudflare ecosystem.

Instructions

List SSL certificate packs for a zone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_nameYes

Implementation Reference

  • Handler function that executes the tool logic: resolves zone ID and fetches SSL certificate packs via Cloudflare API, returning formatted JSON in MCP content format.
    handler: async (params: any) => {
      const { zone_name } = params as z.infer<typeof listSslCertsParamsSchema>;
      const zoneId = await getZoneId(zone_name);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(await client.get(`/zones/${zoneId}/ssl/certificate_packs`), null, 2)
          }
        ]
      };
    },
  • Input schema definition using Zod for the tool, validating 'zone_name' parameter.
    const listSslCertsParamsSchema = z.object({
      zone_name: zoneNameSchema,
    });
  • src/index.ts:48-52 (registration)
    Tool name sanitization replacing '/' with '_', registering 'cloudflare-dns-mcp/list_ssl_certs' as 'cloudflare-dns-mcp_list_ssl_certs' in the toolsMap used by the MCP server.
    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;
    }
  • Local registration of the tool in the ssl-certs module's tools record (overrides any prior definitions).
    return {
      'cloudflare-dns-mcp/list_ssl_certs': listSslCertsTool,
      'cloudflare-dns-mcp/order_ssl_cert': orderSslCertTool,
      'cloudflare-dns-mcp/upload_custom_certificate': uploadCustomCertTool,
    };
  • Helper function to resolve zone name to zone ID, used by the handler.
    function makeHelpers(client: CloudflareClient) {
      return {
        getZoneId: async (zoneName: string): Promise<string> => {
          const zones = await client.get<Array<{ id: string; name: string }>>('/zones', { name: zoneName });
          if (zones.length === 0) throw new Error(`Zone ${zoneName} not found`);
          return zones[0].id;
        },
      };
    }
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. It states it's a list operation, implying read-only behavior, but doesn't disclose any behavioral traits such as pagination, rate limits, authentication needs, or what 'packs' entails (e.g., bundled certificates). The description is minimal and lacks necessary context for safe invocation.

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, clear sentence with zero waste—it directly states the action and resource. It's appropriately sized and front-loaded, making it easy to parse quickly without unnecessary elaboration.

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 no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on behavioral aspects (e.g., response format, error handling) and parameter semantics. For a tool with one parameter but no structured support, more context is needed to ensure reliable use.

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 'for a zone', which aligns with the 'zone_name' parameter in the schema. However, schema description coverage is 0%, and the description doesn't add meaning beyond this basic mapping. It doesn't explain what 'zone_name' should be (e.g., domain name, ID) or any constraints. With one parameter and low coverage, this is adequate but minimal.

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 ('List') and resource ('SSL certificate packs for a zone'), making the purpose specific and understandable. It distinguishes from siblings like list_dns_records or list_zones by focusing on SSL certificates. However, it doesn't explicitly differentiate from all siblings (e.g., list_waf_rules) beyond the resource type.

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. It doesn't mention prerequisites, when-not scenarios, or compare with other list tools (e.g., list_zones for zones vs. list_ssl_certs for certificates). Usage is implied by the resource focus, but explicit context is missing.

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