Skip to main content
Glama

manageLists

Manage allow, deny, and block lists for a NextDNS profile. Add, remove, or replace entries to control domain filtering, privacy blockers, parental controls, and security settings.

Instructions

Manage allow/deny/block lists for a NextDNS profile.

List types: - allowlist / denylist: Always-allow or always-block specific domains. - privacy_blocklists: Subscribed blocklists (e.g., nextdns-recommended). - privacy_natives: Native tracking blockers (e.g., apple, facebook). - security_tlds: Dangerous top-level domains to block (e.g., zip). - parental_categories: Content categories (e.g., gambling, porn). - parental_services: Specific apps/services (e.g., tiktok, youtube).

Operations: - get: Return the current list. - add: Append one entry (pass entry as {"id": "value"} or as a plain id string). - remove: Delete one entry by entry_id. - update: Toggle an existing entry by entry_id (pass entry={"active": True|False}). Only supported for allowlist, denylist, parental_categories, and parental_services. - replace: Replace the entire list with entries (list of dicts).

Examples: - get: manageLists(list_type="denylist", operation="get", profile_id="abc123") - add: manageLists(list_type="denylist", operation="add", profile_id="abc123", entry={"id": "example.com"}) - remove: manageLists(list_type="denylist", operation="remove", profile_id="abc123", entry_id="example.com") - replace: manageLists(list_type="privacy_blocklists", operation="replace", profile_id="abc123", entries=[{"id": "nextdns-recommended"}])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entryNo
entriesNo
entry_idNo
list_typeYes
operationYes
profile_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description fully covers behavioral aspects: it details CRUD operations, which lists support 'update', and how parameters work (e.g., entry vs entry_id). It does not mention rate limits or authentication, but these are standard.

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 well-structured with bullet points and code examples, but it is somewhat lengthy. Each section earns its place, though some redundancy could be trimmed (e.g., repeated example usage patterns).

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?

For a tool with 6 parameters, 7 list types, and 5 operations, the description is nearly complete. It explains all operations and types, and provides usage examples. It does not describe the output schema, but given an output schema exists, that gap is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description adds rich meaning: it explains each list type's purpose, operation semantics, parameter formats (e.g., entry can be a string or dict), and provides concrete examples, fully compensating for the sparse schema.

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 explicitly states the tool manages allow/deny/block lists for NextDNS profiles, enumerates all list types and operations, and distinguishes itself from sibling tools like dohLookup or manageSettings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context for each operation and list type is provided, with examples. However, there is no explicit guidance on when not to use this tool or direct comparison to alternatives, but siblings are clearly different.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dmeiser/nextdns-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server