Skip to main content
Glama
dmeiser

nextdns-mcp

by dmeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Manageprofiles

manageProfiles

Create, list, retrieve, update, or delete NextDNS profiles to get profile IDs needed for DNS settings, blocklists, analytics, and logs.

Instructions

Manage NextDNS profiles.

NextDNS profiles are named configurations that contain DNS settings, blocklists, analytics, and logs. Most other tools require a profile_id from this tool.

Operations: - list: Return profiles the API key can access (supports cursor for pagination). - create: Create a new profile (requires name). - get: Retrieve a single profile (requires profile_id). - update: Rename a profile (requires profile_id and name). - delete: Remove a profile (requires profile_id).

Examples: - list: manageProfiles(operation="list") - list (page): manageProfiles(operation="list", cursor="j2k3zl3b4v") - create: manageProfiles(operation="create", name="Home Network") - get: manageProfiles(operation="get", profile_id="abc123")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
cursorNo
operationYes
profile_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.2.0
    • addedInput schema / properties / cursor
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
  2. Addedv3.0.1

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose useful traits beyond the schema, such as cursor-based pagination for list and that delete removes a profile, but it omits permission requirements, irreversibility of delete, and rate-limit behavior, leaving meaningful gaps for a mutation-capable tool.

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 structure is excellent: a one-line purpose, an operations list with per-op requirements, and concrete call examples. It is slightly verbose since the examples partly restate the operations list, but every block adds routing value for a multi-operation tool.

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?

An output schema exists, so return values need no explanation, and the description covers all operations, their parameters, pagination, and upstream dependency. It is nearly complete; only safety/permission context for destructive operations is missing, which is a modest gap.

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?

Schema description coverage is 0%, so the description must compensate, and it largely does: it maps each operation to its required parameters (create→name, get/delete→profile_id, update→profile_id+name) and explains cursor's pagination role. All four parameters are given meaning, though name/cursor formats remain unspecified.

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 states a specific resource (NextDNS profiles) and enumerates the five distinct operations it performs (list/create/get/update/delete). It also distinguishes itself from siblings by noting that most other tools require a profile_id obtained from this tool, so an agent can place it in the workflow without opening any schema.

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?

It clearly routes usage: most other tools depend on a profile_id sourced here, and each operation lists its required inputs. There is no explicit when-not-to-use guidance or exclusion of sibling tools, so it falls short of a full 5 despite the strong context provided.

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