Skip to main content
Glama
Panelica

panelica-mcp

Official
by Panelica

panelica_cloudflare_delete_v1_cloudflare_zones_zone_id__5d0d4625

Remove a DNS record from a Cloudflare zone by specifying the zone ID and record ID.

Instructions

Delete a DNS record from a CloudFlare zone.

HTTP: DELETE /v1/cloudflare/zones/:zone_id/dns/:record_id Category: CloudFlare

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_idYesPath parameter: zone_id
record_idYesPath parameter: record_id
credential_idNoQuery parameter: credential_id
Behavior2/5

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

With no annotations, the description fails to add behavioral context beyond stating it's a delete operation. It does not mention irreversibility, permission requirements, or side effects like cache purging.

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 description is very short (3 sentences) and front-loaded with the action. However, inclusion of HTTP path and category may be redundant for an AI agent.

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?

No output schema or explanation of return values. The description does not clarify the optional credential_id parameter or deletion behavior, leaving gaps for reliable tool selection.

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?

Input schema has 100% coverage with simple descriptions like 'Path parameter: zone_id'. The tool description adds no further semantics, so baseline 3 applies.

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?

The description clearly states 'Delete a DNS record from a CloudFlare zone.' It uses a specific verb and resource, distinguishing it from sibling tools like panelica_cloudflare_get_v1_cloudflare_zones_zone_id_dns (list) and panelica_cloudflare_post_v1_cloudflare_zones_zone_id_dns (create).

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 is provided on when to use this tool versus alternatives like panelica_dns_delete_v1_dns_records_id (non-CloudFlare DNS delete). It also lacks prerequisites or context for when deletion is appropriate.

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

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/Panelica/panelica-mcp'

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