Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a DNS record

eurodns_dns_delete_record
DestructiveIdempotent

Deletes a single DNS record from a zone, specifying either the numeric record ID or the record type, host, and exact value to disambiguate. Returns the deleted record.

Instructions

Deletes one DNS record from the zone domainName, either by its numeric recordId or by type and host, resolving the id from the live zone in the second case, and returns what was deleted. Give rdata as well when several records share a type and host: an ambiguous selection is refused rather than guessed, and so is a record the provider locked. Read the zone first with eurodns_dns_get_zone to see what it holds; to remove many records at once, save a complete zone with eurodns_dns_save_zone instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoNode the record applies to. Use "" or "@" for the apex. Required without recordId.
typeNoRecord type of the record to delete, e.g. A, CNAME, TXT. Required without recordId.
rdataNoExact current value, to disambiguate.
recordIdNoNumeric id of the record, from the records eurodns_dns_get_zone returns. When given, type and host are not needed.
domainNameYesZone to modify, e.g. example.com.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneYes
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.10.0
    • changedInput schema / properties / host / description
      Previous value: -"Node the record applies to. Use \"\" or \"@\" for the apex."New value: +"Node the record applies to. Use \"\" or \"@\" for the apex. Required without recordId."
    • addedInput schema / properties / recordId
      Added value: +{
+  "description": "Numeric id of the record, from the records eurodns_dns_get_zone returns. When given, type and host are not needed.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • changedInput schema / properties / type / description
      Previous value: -"Record type of the record to delete."New value: +"Record type of the record to delete, e.g. A, CNAME, TXT. Required without recordId."
    • changedInput schema / required
      Previous value: -[
-  "domainName",
-  "type",
-  "host"
-]New value: +[
+  "domainName"
+]
    • changedOutput schema / properties / deleted / required
      Previous value: -[
-  "id",
-  "type",
-  "host",
-  "rdata"
-]New value: +[
+  "id"
+]
  2. First observedv0.9.1

TDQS

A5/5.0
Behavior5/5

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

The annotations already mark the operation as destructive, open-world, and idempotent. The description goes beyond these by detailing the exact rejection behavior for ambiguous and locked records, and clarifying that recordId supersedes type and host. No contradiction with annotations.

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 compact, uses parallel structure, and packs essential usage details without redundancy. Each sentence adds distinct information: primary action, disambiguation rule, and guidance to consult sibling tools.

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?

Given the annotations (destructive, open-world, idempotent) and the schema (full parameter coverage), the description completes the picture by explaining failure modes and the recommended workflow. An agent has enough context to call this tool correctly and safely.

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

Parameters5/5

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

The schema covers all five parameters with detailed descriptions, including requirements ('Required without recordId') and enums for type. The description reinforces the meaning of rdata as an exact current value and clarifies the apex representation, adding value beyond the schema.

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 the tool deletes a DNS record from a zone, specifies the two identification methods (recordId or type+host), and names the sibling tools for reading and bulk updates. It fully distinguishes this from eurodns_dns_get_zone and eurodns_dns_save_zone.

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 explicitly advises reading the zone first with eurodns_dns_get_zone, explains when rdata is needed for disambiguation, and contrasts with mass removal via eurodns_dns_save_zone. It also explains rejection of ambiguous or locked records, giving clear usage conditions.

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

Deploy Server

Other Tools