eurodns-mcp

Get a zone profile, or list them

eurodns_dns_get_zone_profile

Read-onlyIdempotent

Retrieve a complete DNS zone profile by ID, or list profiles with optional name filtering and pagination. These profile templates define records, URL forwards, and mail forwards for new zones.

Instructions

Returns one zone profile in full — name, records, URL forwards and mail forwards — by id, or lists the account’s profiles, filtered by name and paged, when id is omitted. Profiles are templates for new zones, not live zones: for the records a domain actually serves use eurodns_dns_get_zone instead. Read a profile before eurodns_dns_save_zone_profile, which replaces the whole profile with what you send; an id that does not exist answers 404.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Numeric id of the profile to return in full. Omit it to list the account’s zone profiles, optionally filtered by name.
`name`	No	Filter on the profile name. Omit to list every profile.
`page`	No	1-based page number. There is no page meaning everything: walk pages until a short one comes back.
`size`	No	Results per page, 1 to 500. A wide page is truncated by the character limit, so prefer a filter to a large size.
`sortField`	No	Result field to sort on, spelled as in the response items. Unsorted when omitted.
`sortOrder`	No	ASC or DESC; only read with sortField.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	Response body as returned by the API.
`status`	Yes	Upstream HTTP status code.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.10.0Sep 7, 2026

changedInput schema / properties / id / description

Previous value: -"id of zone profile to return"New value: +"Numeric id of the profile to return in full. Omit it to list the account’s zone profiles, optionally filtered by name."

addedInput schema / properties / name

Added value: +{
+  "description": "Filter on the profile name. Omit to list every profile.",
+  "type": "string"
+}

addedInput schema / properties / page

Added value: +{
+  "description": "1-based page number. There is no page meaning everything: walk pages until a short one comes back.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / size

Added value: +{
+  "description": "Results per page, 1 to 500. A wide page is truncated by the character limit, so prefer a filter to a large size.",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / sortField

Added value: +{
+  "description": "Result field to sort on, spelled as in the response items. Unsorted when omitted.",
+  "type": "string"
+}

addedInput schema / properties / sortOrder

Added value: +{
+  "description": "ASC or DESC; only read with sortField.",
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "id"
-]
```

First observedv0.9.1Sep 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description discloses meaningful behaviors beyond the annotations, such as the 404 response for a nonexistent id, pagination walk behavior, and the truncation risk with wide pages. Combined with the readOnly, idempotent, and non-destructive annotations, the agent can fully predict side effects.

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 dense but well-organized, packing purpose, variants, usage guidance, and edge-case behavior into a compact form. Every sentence adds practical value without redundancy or fluff.

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 moderate complexity of a paginated fetch-or-list tool, the description covers all essential context: resource semantics, live-zone alternative, save-profile prerequisite, pagination behavior, sort constraints, and error behavior. Nothing important is missing for correct invocation.

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?

The input schema already covers all parameters with high-quality descriptions, so the baseline is strong. The description adds useful caveats beyond the schema, such as sortOrder only being read with sortField, and the recommendation to prefer filters over large page sizes due to character-limit truncation.

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's dual purpose: return one zone profile by id, or list the account's profiles filtered by name and paged when id is omitted. It also specifies the resource type (zone profiles) and distinguishes them from live zones.

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?

It explicitly says profiles are templates, not live zones, and directs users to eurodns_dns_get_zone for live zone records. It also advises reading a profile before calling eurodns_dns_save_zone_profile, giving clear when-to-use guidance relative to sibling tools.

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

Deploy Server