Skip to main content
Glama

Create DNS record

create_dns_record

Creates a new DNS record for a domain and returns the stored record with its new ID, enabling DNS configuration changes such as adding A, CNAME, MX, or TXT entries.

Instructions

Create a new DNS record for a domain. Returns the stored record, including its new ID.

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>",
      "host": "<host>",
      "type": "<type>",
      "data": "<data>"
    },
    "name": "create_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
algNorequired for DS: the DNSSEC signing algorithm number, 0-255
tagNorequired for DS as a number (the key tag 0-65535 of the referenced DNSKEY) and for CAA as a string (the property tag, e.g. issue, issuewild or iodef)
ttlNotime-to-live in seconds, 60-604800, must be a multiple of 60, defaults to 3600
dataYesthe record's main value: an IPv4 address for A, an IPv6 address for AAAA, a hostname for ANAME/CNAME/MX/NS/SRV, free text for TXT, the CAA property value, or the hex hash for DS/TLSA
hostYesthe host/subdomain the record applies to, e.g. 'www' or '@' for the root
portNorequired for SRV: the port 0-65535 the service is found on
typeYesthe record type
dtypeNorequired for TLSA: matching type of the hash in data (0 exact match, 1 SHA-256, 2 SHA-512)
flagsNorequired for CAA: 128 to mark the property critical, otherwise 0
usageNorequired for TLSA: certificate usage (0 PKIX-TA, 1 PKIX-EE, 2 DANE-TA, 3 DANE-EE)
digestNorequired for DS: digest type of the hash in data (1 SHA-1, 2 SHA-256, 4 SHA-384)
weightNorequired for SRV: relative weight 0-65535 among records with the same priority
priorityNorequired for MX and SRV: preference value 0-65535, lower is tried first
selectorNorequired for TLSA: what the hash is taken from (0 full certificate, 1 subject public key)
domain_idYesthe Domeneshop domain ID, from list_domains

Output Schema

NameRequiredDescriptionDefault
idNo
algNo
tagNo
ttlNo
dataYes
hostYes
portNo
typeYes
dtypeNo
flagsNo
usageNo
digestNo
weightNo
priorityNo
selectorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed27 schema fields changedv2.0.0
    • changedInput schema / properties / alg / description
      Previous value: -"required for DS: the DNSSEC signing algorithm number"New value: +"required for DS: the DNSSEC signing algorithm number, 0-255"
    • changedInput schema / properties / alg / maximum
      Previous value: -9007199254740991New value: +255
    • changedInput schema / properties / alg / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / data / description
      Previous value: -"the record's main value: an IP address for A/AAAA, a hostname for ANAME/CNAME/MX/NS/SRV, free text for TXT, the CAA property value, or the hex hash for DS/TLSA"New value: +"the record's main value: an IPv4 address for A, an IPv6 address for AAAA, a hostname for ANAME/CNAME/MX/NS/SRV, free text for TXT, the CAA property value, or the hex hash for DS/TLSA"
    • addedInput schema / properties / data / minLength
      Added value: +1
    • changedInput schema / properties / digest / maximum
      Previous value: -9007199254740991New value: +255
    • changedInput schema / properties / digest / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / dtype / maximum
      Previous value: -9007199254740991New value: +2
    • changedInput schema / properties / dtype / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / flags / maximum
      Previous value: -9007199254740991New value: +255
    • changedInput schema / properties / flags / minimum
      Previous value: --9007199254740991New value: +0
    • addedInput schema / properties / host / minLength
      Added value: +1
    • changedInput schema / properties / port / description
      Previous value: -"required for SRV: the port the service is found on"New value: +"required for SRV: the port 0-65535 the service is found on"
    • changedInput schema / properties / priority / description
      Previous value: -"required for MX and SRV: preference value, lower is tried first"New value: +"required for MX and SRV: preference value 0-65535, lower is tried first"
    • changedInput schema / properties / priority / maximum
      Previous value: -9007199254740991New value: +65535
    • changedInput schema / properties / priority / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / selector / maximum
      Previous value: -9007199254740991New value: +1
    • changedInput schema / properties / selector / minimum
      Previous value: --9007199254740991New value: +0
    • addedInput schema / properties / tag / anyOf
      Added value: +[
      +  {
      +    "maximum": 65535,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / tag / description
      Previous value: -"required for DS (the key tag of the referenced DNSKEY) and for CAA (the property tag, e.g. issue, issuewild or iodef)"New value: +"required for DS as a number (the key tag 0-65535 of the referenced DNSKEY) and for CAA as a string (the property tag, e.g. issue, issuewild or iodef)"
    • removedInput schema / properties / tag / type
      Removed value: -[
      -  "number",
      -  "string"
      -]
    • changedInput schema / properties / usage / maximum
      Previous value: -9007199254740991New value: +3
    • changedInput schema / properties / usage / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / weight / description
      Previous value: -"required for SRV: relative weight among records with the same priority"New value: +"required for SRV: relative weight 0-65535 among records with the same priority"
    • changedInput schema / properties / weight / maximum
      Previous value: -9007199254740991New value: +65535
    • changedInput schema / properties / weight / minimum
      Previous value: --9007199254740991New value: +0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "alg": {
      +      "type": "number"
      +    },
      +    "data": {
      +      "type": "string"
      +    },
      +    "digest": {
      +      "type": "number"
      +    },
      +    "dtype": {
      +      "type": "number"
      +    },
      +    "flags": {
      +      "type": "number"
      +    },
      +    "host": {
      +      "type": "string"
      +    },
      +    "id": {
      +      "type": "number"
      +    },
      +    "port": {
      +      "type": "number"
      +    },
      +    "priority": {
      +      "type": "number"
      +    },
      +    "selector": {
      +      "type": "number"
      +    },
      +    "tag": {
      +      "type": [
      +        "number",
      +        "string"
      +      ]
      +    },
      +    "ttl": {
      +      "type": "number"
      +    },
      +    "type": {
      +      "type": "string"
      +    },
      +    "usage": {
      +      "type": "number"
      +    },
      +    "weight": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "host",
      +    "type",
      +    "data"
      +  ],
      +  "type": "object"
      +}
  3. First observedv1.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is covered. The description confirms a record is persisted and an ID assigned, which is useful, but adds nothing on failure modes, duplicate-record behavior, or propagation/permission requirements beyond what annotations and the output schema supply.

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?

Two short sentences, front-loaded with the action and followed by the result. No filler, no repetition of schema content.

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?

With 15 parameters and 11 type-dependent conditional fields, this is a moderately complex tool; the description does not note that the required field set varies by record type, nor warn that duplicate records may not be rejected given idempotentHint=false. The rich schema and existing output schema prevent this from being a serious gap, making it adequate but thin.

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 description coverage is 100%, and the schema itself spells out the type-conditional requirements (priority for MX/SRV, digest/alg/tag for DS, usage/selector/dtype for TLSA, flags for CAA, ttl defaults). The description contributes nothing further, so the baseline 3 applies.

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?

"Create a new DNS record for a domain" states a specific verb and resource, and the return clause clarifies the outcome. It doesn't explicitly contrast with update_dns_record or upsert_dns_record in the sibling list, but the create semantics are unambiguous from the name and text.

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?

The description offers no when-to-use guidance: nothing says when to prefer this over upsert_dns_record or patch_dns_record, and no preconditions (such as needing an existing domain_id from list_domains) are stated. A caller must infer the choice entirely from the tool name.

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