Skip to main content
Glama

Edit DNS record

edit_dns_record
Destructive

Replace the value of one existing DNS record; its type, name and TTL stay. The old value is overwritten without undo, so note it from list_dns_records if it may need to come back. Take recordId from a list_dns_records call made just before: it is the record's position in the zone and shifts when records are added or removed. To change the type or name, delete the record and add a new one. Resolvers can keep the old value up to the record's TTL.

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": {
      "id": "<id>",
      "recordId": "<recordId>",
      "data": "<data>"
    },
    "name": "edit_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe domain ID
dataYesNew value, in the format the record's type expects (an IP for A, a hostname for CNAME, the text for TXT)
recordIdYesrecordId from a list_dns_records call made just before this one

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds real operational context on top: the old value is overwritten with no undo, the prior value should be captured from list_dns_records, and resolvers may serve the stale value until TTL expiry. Those are consequences an agent could not derive from the annotations alone.

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?

Four short sentences, each carrying distinct information, with the destructive core stated first and the recovery path and TTL caveat following. No filler or restatement of the title.

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 three-parameter mutation tool with no output schema, the description covers irreversibility, how to recover the prior value, identifier volatility, the alternative workflow for type/name changes, and propagation delay. Nothing an agent needs to invoke it safely is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, and the description earns an extra point by explaining that recordId is the record's position in the zone and shifts when neighbouring records are added or removed. The data format hint partially duplicates the schema but reinforces the type-dependent value format.

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?

"Replace the value of one existing DNS record" names a specific verb (replace) and resource (DNS record) and immediately bounds the scope: type, name and TTL stay unchanged. An agent can distinguish this from add_dns_record and delete_dns_record without opening any schema.

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?

Explicit routing is provided: use delete + add when the type or name must change, and call list_dns_records immediately beforehand to obtain recordId. Both the when-to-use and the when-not-to-use case are stated rather than inferred.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.