Skip to main content
Glama
Sign In
UniFi MCP Server

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

connector_network_post

Send POST requests to the UniFi Network Application through Cloud Connector to update network configuration. Use dry-run previews and confirmation to control mutating changes.

Instructions

Proxy a POST 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_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional request body to forward
pathYesNetwork API sub-path, e.g. ``api/s/default/rest/wlanconf``
confirmNoMust be True to execute (mutating operation)
dry_runNoIf True, preview the request without sending it
console_idYesUniFi console/host identifier (from list_hosts)
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. Changed9 schema fields changedv0.6.4
    • addedInput schema / properties / body / description
      Added value: +"Optional request body to forward"
    • addedInput schema / properties / confirm / description
      Added value: +"Must be True to execute (mutating operation)"
    • addedInput schema / properties / console_id / description
      Added value: +"UniFi console/host identifier (from list_hosts)"
    • addedInput schema / properties / dry_run / description
      Added value: +"If True, preview the request without sending it"
    • addedInput schema / properties / path / description
      Added value: +"Network API sub-path, e.g. ``api/s/default/rest/wlanconf``"
    • 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 behavioral burden. 'POST' signals a write operation, but the description omits critical traits such as the required `confirm=True` gate, `dry_run` preview behavior, authentication requirements, and the fact that arbitrary Network API sub-paths can be called.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with zero waste. It states the core operation immediately and does not bury the purpose in caveats or filler.

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?

This is a powerful generic proxy for mutating Network API calls, and there are no annotations to compensate for the sparse description. While the schema is rich and an output schema exists, the description fails to surface the safety-critical confirmation requirement or the dry-run preview, leaving important operational context only in the parameter descriptions.

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 every parameter thoroughly, including `confirm`, `dry_run`, `path`, `console_id`, and `controller`. The description adds no additional meaning beyond what the schema provides, making the baseline 3 appropriate.

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?

The description states a specific action (proxy a POST request) and target resource (Network Application via Cloud Connector). It implicitly distinguishes this from the sibling GET/PUT/PATCH/DELETE connector tools by naming POST, though it does not explicitly call out those alternatives.

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?

The description provides no when-to-use guidance, no prerequisites, and no mention of alternatives. It does not explain when an agent should use this generic proxy versus a more specific integration tool.

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