UniFi Network MCP Server

by owine

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List DNS policies

unifi_list_dns_policies

Read-only

List DNS policies for a site to view local DNS records and forward rules, including enabled status and record details.

Instructions

List DNS policies (local DNS records and forward rules served by the gateway) at a site. Returns: id, type (A_RECORD, AAAA_RECORD, CNAME_RECORD, MX_RECORD, TXT_RECORD, SRV_RECORD, FORWARD_DOMAIN), enabled, domain, metadata.origin, plus type-specific fields: A ipv4Address+ttlSeconds; AAAA ipv6Address+ttlSeconds; CNAME targetDomain+ttlSeconds; MX mailServerDomain+priority; TXT text; SRV serverDomain/service/protocol/port/priority/weight; FORWARD_DOMAIN ipAddress (per 11.0.83 response samples).

Input Schema

Name	Required	Description
`limit`	No	Number of records to return (API default: 25)
`filter`	No	Filter expression, e.g. type.eq('A_RECORD')
`offset`	No	Number of records to skip
`siteId`	Yes	Site ID

Output Schema

Name	Required	Description	Default
`data`	Yes
`count`	No
`limit`	No
`offset`	No
`totalCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv2.15.0Oct 14, 2026
- changedInput schema / properties / filter / description
```
Previous value: -"Filter expression"New value: +"Filter expression, e.g. type.eq('A_RECORD')"
```
- changedInput schema / properties / limit / description
```
Previous value: -"Number of records to return (default: 25, max: 200)"New value: +"Number of records to return (API default: 25)"
```
- changedInput schema / properties / offset / description
```
Previous value: -"Number of records to skip (default: 0)"New value: +"Number of records to skip"
```
- addedInput schema / properties / siteId / pattern
```
Added value: +"^[A-Za-z0-9_-]{1,64}$"
```
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedOutput schema / properties / data / items / properties / ipAddress
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / data / items / properties / ipv6Address
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / data / items / properties / mailServerDomain
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / data / items / properties / metadata / properties / configurable
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / data / items / properties / port
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / data / items / properties / priority
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / data / items / properties / protocol
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / data / items / properties / serverDomain
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / data / items / properties / service
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / data / items / properties / targetDomain
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / data / items / properties / text
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / data / items / properties / weight
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
Changed1 schema field changedv2.13.0Sep 20, 2026
- changedInput schema / properties / limit / minimum
```
Previous value: -1New value: +0
```
First observedv2.8.0Jun 30, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds the full field shape and the type enum values returned, which is useful behavioral context, but it says nothing about pagination behavior, default page size, or filter syntax beyond echoing the schema.

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?

Purpose and scope are front-loaded in the first clause before the field inventory. The long return-field enumeration is dense but each item earns its place by mapping record types to their fields; it is verbose but not padded.

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?

A read-only list tool with an output schema, complete parameter descriptions and full annotations needs little more than a clear purpose statement, which this supplies. Its only real omission is routing guidance to unifi_get_dns_policy and any note on paging through large result sets.

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%, so limit, offset, filter and siteId are already documented in the schema, and the description adds no parameter meaning on top of that. Baseline 3 is appropriate when structured fields carry the parameter burden.

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+resource ('List DNS policies') and adds a clarifying gloss that these are local DNS records and forward rules served by the gateway. It never names its sibling unifi_get_dns_policy or states it returns a collection rather than one policy, so differentiation is left to the name alone.

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?

There is no when-to-use guidance, no prerequisite (e.g. a valid siteId), and no mention of the alternative unifi_get_dns_policy for fetching a single rule. An agent must infer that this is the enumeration tool from the name only.

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

Deploy Server