Skip to main content
Glama
enuno

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_integration_wifi_broadcasts

List WiFi broadcasts (SSIDs) via the integration API.

Instructions

List WiFi broadcasts (SSIDs) via the integration API.

Args: site_id: Site identifier settings: Application settings limit: Maximum number of broadcasts to return (1-1000) offset: Number of broadcasts to skip

Returns: Paginated list of WiFi broadcasts

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
site_idYes
controllerNoController to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
+}
  2. First observedv0.2.0

TDQS

B3/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 pagination ('Paginated list') and the limit bound (1-1000), which is useful, but it says nothing about authentication requirements, read-only nature beyond the implied 'List', error behavior, or how the default controller is resolved.

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?

Front-loaded purpose followed by compact Args/Returns sections; nothing is padded. The only waste is the phantom 'settings: Application settings' line, which occupies space without matching any real parameter.

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 the terse 'Returns' line is acceptable. However, for a 4-parameter integration tool the description leaves the controller-routing parameter unexplained and includes a stale argument, so it is adequate but not fully complete.

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 only 25% (only 'controller' is documented in the schema), so the description should compensate. It clarifies limit/offset and adds the 1-1000 range, but it omits the important 'controller' parameter entirely and lists a 'settings' argument that does not exist in the schema, which is actively misleading.

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 concrete verb and resource ('List WiFi broadcasts (SSIDs)') plus the API surface ('integration API'), which distinguishes it from the singular get_integration_wifi_broadcast sibling. It is clear what the tool returns, though it never names a sibling or scope boundary explicitly.

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 when-to-use guidance, no mention of when to prefer get_integration_wifi_broadcast over this list variant, and no note about required controller selection despite many controller-routing siblings. Usage is only implied by the verb 'List'.

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