Skip to main content
Glama
UniFi MCP Server

UniFi MCP Server

connector_protect_delete

Send a DELETE request to a UniFi Protect API sub-path through the Cloud Connector, using a console ID and optional dry-run or confirmation controls.

Instructions

Proxy a DELETE request to the Protect 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_protect_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesProtect API sub-path
confirmNoMust be True to execute
dry_runNoPreview without sending
console_idYesUniFi console/host identifier
controllerNoController to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.6.4
    • 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: +"Protect 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
  2. Changed1 schema field changedv0.6.0
    • 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."
      +}
  3. First observedv0.2.0

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 burden for a destructive operation. It says DELETE is proxied but never states that deletion is irreversible, that confirm must be true to execute, that dry_run previews safely, or what permissions/credentials are needed against the console.

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?

A single tight sentence with no filler wastes nothing. It is well front-loaded, though it is arguably too terse for a destructive proxy tool rather than genuinely optimal.

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

Completeness3/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-value explanation is not required, and the schema fully documents the parameters. What is missing is the safety context an agent needs before firing a DELETE: the confirm gate and irreversibility, which the description should surface given the absence of annotations.

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%, with confirm, dry_run, controller and path all documented in the schema, so the baseline of 3 applies. The description adds no syntax, path-format, or controller-resolution detail beyond what the schema already states.

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 (proxy a DELETE) and a specific resource/target (Protect Application via Cloud Connector), which cleanly separates it from the sibling methods connector_protect_get/post/patch/put. It is, however, a generic passthrough, so what is actually being deleted is deferred entirely to the caller-supplied path.

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 guidance on when to choose this over connector_protect_post/put/patch or over the higher-level Protect tools. Nothing in the description mentions the confirm or dry_run gating, which is the key precondition for actually invoking a delete.

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