NextDNS-Agent-MCP

list_entries

Idempotent

Add, remove, turn on, or turn off domains in a NextDNS profile's allowlist or denylist; returns change ID so updates can be undone.

Instructions

Add, remove, turn on or turn off domains in a profile's denylist (always blocked) or allowlist (never blocked); a domain also covers its subdomains. Use it for single domains; use parental_control for whole apps or categories, privacy for blocklists, and check_domain first to see why a domain is blocked. Changes the profile within seconds and records it, so undo can put it back. Returns what was done, what was skipped (already there, not there) or failed (not a domain), and the change ID.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	add, remove, on (turn an entry back on) or off (keep it, but not in use).
`domains`	Yes	Up to 100 domains, like example.com. A domain also covers its subdomains; links are cut down to the domain.
`profile`	No	The profile's ID or name. Leave empty for the only profile, or the default one.
`list_name`	Yes	Which list: denylist (always blocked) or allowlist (never blocked).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 21, 2026

addedInput schema / properties / action / description

Added value: +"add, remove, on (turn an entry back on) or off (keep it, but not in use)."

addedInput schema / properties / domains / description

Added value: +"Up to 100 domains, like example.com. A domain also covers its subdomains; links are cut down to the domain."

addedInput schema / properties / list_name / description

Added value: +"Which list: denylist (always blocked) or allowlist (never blocked)."

addedInput schema / properties / profile / description

Added value: +"The profile's ID or name. Leave empty for the only profile, or the default one."

First observedv0.8.1Oct 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, it discloses that changes apply within seconds, are recorded, and can be undone via undo. It also summarizes return outcomes: what was done, skipped, failed, and the change ID. This adds useful operational context while staying consistent with readOnlyHint=false and destructiveHint=false.

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?

The description is front-loaded with the core operation and every sentence carries relevant information. It is slightly dense and semicolon-heavy, but it does not waste space or bury the purpose.

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 annotations and output schema, the description covers the remaining gaps: purpose, alternatives, timing, undo behavior, and return outcomes. Nothing important for selecting or invoking the tool appears missing.

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 the schema already documents all parameters, including action, domains, profile, and list_name. The description reinforces denylist/allowlist and single-domain semantics but adds little beyond the schema, making the baseline 3 appropriate.

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 specifies the exact resource and operations: adding, removing, turning on, or turning off domains in a profile's denylist or allowlist. It also distinguishes this from siblings like parental_control, privacy, and check_domain, so an agent can identify the tool's role without opening the 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?

It explicitly says to use this for single domains and names alternatives for whole apps/categories (parental_control), blocklists (privacy), and diagnosis (check_domain). This gives clear when-to-use and when-not-to-use guidance.

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