Skip to main content
Glama

Delete DNS record

delete_dns_record
DestructiveIdempotent

Permanently removes a DNS record from a Domeneshop domain using its domain ID and record ID; deletion cannot be undone.

Instructions

Delete a DNS record. This cannot be undone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain_id": "<domain_id>",
      "record_id": "<record_id>"
    },
    "name": "delete_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_idYesthe Domeneshop domain ID, from list_domains
record_idYesthe DNS record ID to delete, from list_dns_records

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.7
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is structured data. The description reinforces irreversibility, which adds a little emphasis and is the main thing the schema doesn't say, but it omits what happens to related records, whether the call fails if record_id is stale, and any permission or confirmation requirements.

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?

Two short sentences, the verb-and-resource statement front-loaded with the destructive warning immediately after. There is no filler, though the warning partially restates destructiveHint rather than spending those words on new behavior.

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

Completeness3/5

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

For a destructive, irreversible mutation with a rich annotation block this is minimally adequate: the agent knows what is deleted and that it is permanent. It is incomplete on post-condition behavior and failure modes, but the annotations and fully documented schema offset much of that.

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?

Schema coverage is 100% and both parameters are documented with their sources (list_domains, list_dns_records), so the schema carries the parameter burden. The description adds no meaning about the identifiers beyond what the schema already provides, making the baseline 3 correct.

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 gives a specific verb plus resource ("Delete a DNS record"), which cleanly separates it from create_dns_record, update_dns_record, patch_dns_record, and upsert_dns_record in the sibling list. It does not explicitly name those siblings as alternatives, so it stops short of a 5.

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

Usage Guidelines3/5

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

"This cannot be undone" implies caution and therefore implies a verification step, but it never says to confirm existence first via get_dns_record or to prefer update_dns_record when only a value change is intended. Usage must be inferred rather than read.

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