Skip to main content
Glama
Sign In
OnlyDNS MCP Server

OnlyDNS MCP Server

Official
by Onlydns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_records

Lists all DNS records for a domain, with optional filtering by record type or hostname, to inspect and verify zone entries.

Instructions

List all DNS records for a domain, with optional filtering by record type (A, AAAA, CNAME, MX, TXT, etc.) or hostname.

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": {
      "domainName": "<domainName>"
    },
    "name": "list_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFilter by record name/hostname. Accepts relative subdomain (e.g. "testing", "@", "www"), domain-qualified name (e.g. "testing.example.com"), or full canonical FQDN (e.g. "testing.example.com.").
typeNoFilter by record type (e.g. A, AAAA, CNAME, MX, TXT, SRV, CAA, NS)
domainNameYesThe domain name to list records for (e.g. example.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.5
    • changedInput schema / properties / name / description
      Previous value: -"Filter by record name/hostname (e.g. \"www\", \"sub.example.com\", or \"@\" for root)"New value: +"Filter by record name/hostname. Accepts relative subdomain (e.g. \"testing\", \"@\", \"www\"), domain-qualified name (e.g. \"testing.example.com\"), or full canonical FQDN (e.g. \"testing.example.com.\")."
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. "List" implies a non-destructive read, which is the main behavioral signal, but it discloses nothing about pagination, result limits, permissions, or result ordering — the details that matter for a listing tool with zero annotation coverage.

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?

A single front-loaded sentence with the resource, scope, and optional filters in the first few words; no filler or redundancy.

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

Completeness4/5

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

With no output schema and no annotations, the description should cover what comes back; "List all DNS records" is minimal but sufficient for a straightforward read tool whose parameters are fully specified in the schema. Return shape and any paging behavior remain unstated, which keeps it short of a 5.

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%, so all three parameters are already fully documented, including the accepted hostname formats and record-type values. The description restates those filters at a high level but adds no syntax or semantics beyond the schema, so 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?

States a specific verb and resource ("List all DNS records for a domain") plus the two optional filter dimensions, so an agent knows exactly what it does. It is distinguishable from add_record/update_record/delete_record by the verb, but does not explicitly differentiate from list_domains or set_records.

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?

The description makes the usage context clear (listing records for a given domain, with optional narrowing by type or hostname) but names no alternatives or exclusions — e.g. it never routes the agent to get_domain_tsig or list_domains, nor states when not to filter.

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