UniFi MCP Server

Overview Schema Source Related Servers Discussions Admin

connector_network_delete

Send a DELETE request to the UniFi Network Application via Cloud Connector to remove API resources, with optional dry-run preview and confirmation before execution.

Instructions

Proxy a DELETE request to the Network Application via Cloud Connector.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "console_id": "<console_id>",
      "path": "<path>"
    },
    "name": "connector_network_delete"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Network API sub-path
`confirm`	No	Must be True to execute
`dry_run`	No	Preview without sending
`console_id`	Yes	UniFi console/host identifier
`controller`	No	Controller to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.6.4Oct 27, 2026

addedInput schema / properties / confirm / description
```
Added value: +"Must be True to execute"
```
addedInput schema / properties / console_id / description
```
Added value: +"UniFi console/host identifier"
```
addedInput schema / properties / dry_run / description
```
Added value: +"Preview without sending"
```
addedInput schema / properties / path / description
```
Added value: +"Network API sub-path"
```
removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "result": {
+    "anyOf": [
+      {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      {
+        "items": {},
+        "type": "array"
+      }
+    ]
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "result"
+]
```
addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```

Changed1 schema field changedv0.6.0Oct 12, 2026

addedInput schema / properties / controller

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Controller to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default."
+}

First observedv0.2.0Jun 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it says nothing about irreversibility, required permissions, or the safety gate implied by the confirm parameter. A destructive passthrough tool with zero annotation coverage needs more than a single sentence about the HTTP method.

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?

One sentence with no padding, and the method/system/channel information is front-loaded. It is efficient, but its brevity is also what leaves the behavioral gaps.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter destructive proxy with no annotations, the description omits the confirm/dry_run execution model, error behavior for invalid sub-paths, and any hint of scope limits. An output schema exists, so return values needn't be explained, but the invocation-safety context is 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% and the schema already explains path, confirm, dry_run, console_id and controller resolution. The description adds nothing beyond that, so the baseline of 3 applies.

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?

States a specific verb and transport ('DELETE request'), the target system ('Network Application') and the channel ('via Cloud Connector'), which cleanly separates it from the connector_network_get/post/patch/put siblings. It stops short of saying what kinds of resources are deletable, since the path is arbitrary.

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?

No guidance on when to choose this over connector_network_patch or connector_network_put, and no mention of the confirm/dry_run workflow that governs whether the call actually executes. The agent must infer the intended usage from the sibling names and the schema alone.

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

Deploy Server