UniFi MCP

network_update_wifi

Update an existing WiFi SSID configuration on a UniFi site, modifying network settings and security options.

Instructions

Update an existing WiFi broadcast (SSID) on a local UniFi site.

Args: site_id: The site ID. wifi_id: The WiFi broadcast ID to update. data: Updated WiFi configuration.

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": {
      "site_id": "<site_id>",
      "wifi_id": "<wifi_id>",
      "data": "<data>"
    },
    "name": "network_update_wifi"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes
`site_id`	Yes
`wifi_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It only says 'update', but lacks disclosure of side effects, error behavior (e.g., if wifi_id does not exist), or required permissions. The flexible 'data' object could have destructive consequences without warning.

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 succinct and front-loaded. The docstring-style parameter list is somewhat redundant with the schema but adds a tiny bit of context. No extraneous sentences.

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?

The tool has an output schema (not shown) but the description omits return value details. The undefined 'data' object creates a significant gap. No examples or usage hints are provided, making the description incomplete for a complex update operation.

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

Parameters2/5

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

Schema coverage is 0%, yet the description only restates parameter names with minimal context (e.g., 'data: Updated WiFi configuration'). No explanation of valid properties for 'data' or constraints, leaving the agent guessing.

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 clearly states the action (update), resource (existing WiFi broadcast/SSID), and context (local UniFi site). It distinguishes itself from sibling CRUD tools like network_create_wifi and network_delete_wifi.

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 use this tool versus alternatives (e.g., network_create_wifi for new SSIDs, network_delete_wifi for removal). No prerequisites or conditions are mentioned.

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

Deploy Server