UniFi Network MCP Server

Overview Schema Source Related Servers Discussions Admin

unifi_list_sites

Read-only

List all UniFi sites the API key can access and return their IDs, names, and internal references to provide the siteId needed by every other tool.

Instructions

List all sites the API key has access to. Returns: id (the siteId every other tool requires), internalReference, name. Use for: first call in any workflow — almost every other tool needs a siteId.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Number of records to return (default: 25, max: 200)
`filter`	No	Filter expression (e.g., 'name.like(office*)')
`offset`	No	Number of records to skip (default: 0)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`count`	No
`limit`	No
`offset`	No
`totalCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Jun 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds that it returns specific fields (id, internalReference, name) and the context of being a first call, without contradicting annotations.

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?

Two sentences: first states purpose, second states return fields, third gives usage tip. Perfectly concise and front-loaded.

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

Completeness5/5

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

With an output schema present, the description covers the key return fields and the tool's role. It is complete for a simple list tool with optional parameters.

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 coverage is 100% with parameter descriptions. The description does not add parameter details, but implies that no parameters are required for basic listing.

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 ('List all sites') and the resource ('sites the API key has access to'). It also mentions the key returned fields, distinguishing it from siblings that list other resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use for: first call in any workflow — almost every other tool needs a siteId', providing clear guidance on when to use this tool and its role in workflows.

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

Deploy Server