eurodns-mcp

Delete a DNS zone profile

eurodns_dns_delete_zone_profile

DestructiveIdempotent

Delete a DNS zone profile permanently. Confirm the profile ID with get_zone_profile first, as deleted profiles cannot be restored.

Instructions

Deletes the zone profile with that id permanently and returns nothing on success. A profile is a template for new zones, so zones already created from it keep their records; there is no snapshot to restore a template from, so confirm the id and contents with eurodns_dns_get_zone_profile first. To change a profile rather than remove it, use eurodns_dns_save_zone_profile instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Numeric id of the zone profile, from the list eurodns_dns_get_zone_profile returns when called without an id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	Response body as returned by the API.
`status`	Yes	Upstream HTTP status code.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.10.0Sep 7, 2026

changedInput schema / properties / id / description

Previous value: -"id of zone profile to delete"New value: +"Numeric id of the zone profile, from the list eurodns_dns_get_zone_profile returns when called without an id."

First observedv0.9.1Sep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint, idempotentHint), the description adds important behavioral context: deletion is permanent, there is no snapshot to restore from, already-created zones keep their records, and it recommends a pre-check with the get tool. These details substantially inform the agent about side effects and risks.

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 two sentences, tightly packed with purpose, consequences, and guidance. No redundant phrasing or unnecessary details; every sentence adds value.

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

Completeness5/5

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

For a simple delete operation with a single parameter and no output schema, the description covers all essential context: what is deleted, what happens to dependent zones, the permanence, the recommended pre-check, and the alternative tool. This is sufficient for an agent to 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 input schema already fully describes the single parameter 'id' with type and provenance (from the list returned by eurodns_dns_get_zone_profile). The tool description does not add further parameter-specific meaning, so the score rests at the baseline for high schema coverage.

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 explicitly states that the tool deletes a zone profile permanently and returns nothing on success, clearly identifying the action and result. It also distinguishes from related tools by naming eurodns_dns_save_zone_profile as the alternative for changes, so an agent can easily tell what this tool does.

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

Usage Guidelines5/5

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

The description gives explicit guidance on when to use this tool versus alternatives: it recommends confirming the id and contents with eurodns_dns_get_zone_profile first, and instructs to use eurodns_dns_save_zone_profile for modifications instead of deletion. This makes the appropriate usage clear.

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

Deploy Server