UniFi Protect MCP

by owine

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

protect_list_link_stations

Read-only

Retrieve all link stations managed by UniFi Protect, returning details like name, MAC, state, and thread network info.

Instructions

List all link stations managed by UniFi Protect. Returns array; each link station includes: id, modelKey ("linkstation"), name, mac, state, type, guid, isAlarmHub, ledSettings (isEnabled), lastEvent, alarmHub (object), deviceTamperStatus, threadState (network: status, role, networkName, channel, panId, extendedPanId, joinedDeviceCount, errorReason, lastUpdatedAt) (7.3.47 docs).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Array of items returned by the list endpoint

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.13.0Sep 20, 2026

addedOutput schema / properties / result / items / properties / deviceTamperStatus

Added value: +{
+  "description": "Tamper status, added in 7.3.x, e.g. \"tampered\"",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / result / items / properties / guid

Added value: +{
+  "description": "Hardware MODEL GUID, shared by every unit of the same model. NOT a per-device identifier — use `id` to identify a device.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / result / items / properties / threadState

Added value: +{
+  "description": "Thread radio state, added in 7.3.x (object: network — status, role, networkName, channel, panId, extendedPanId, joinedDeviceCount, errorReason, lastUpdatedAt)"
+}

addedOutput schema / properties / result / items / properties / type

Added value: +{
+  "description": "Hardware model name, e.g. \"UVC G6 Turret\", \"UP Chime PoE\", \"UNVR-PRO\"",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed8 schema fields changedv2.11.5Sep 13, 2026
- removedOutput schema / properties / result / items / properties / mac / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / result / items / properties / mac / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / items / properties / modelKey / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / result / items / properties / modelKey / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / items / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / result / items / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / items / properties / state / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / result / items / properties / state / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Addedv2.10.0Jul 29, 2026
Removedv2.9.0Jul 23, 2026

Changed4 schema fields changedv2.7.5Jun 21, 2026

addedOutput schema / properties / result / items / properties / alarmHub

Added value: +{
+  "description": "Alarm hub status (object: armed, battery, connector, cover, output, input, …)"
+}

addedOutput schema / properties / result / items / properties / isAlarmHub

Added value: +{
+  "description": "Whether this device is an alarm hub (boolean)"
+}

addedOutput schema / properties / result / items / properties / lastEvent

Added value: +{
+  "description": "Last event timestamp in epoch ms (number)"
+}

addedOutput schema / properties / result / items / properties / ledSettings
```
Added value: +{
+  "description": "LED settings (object: isEnabled)"
+}
```

First observedv2.7.4Jun 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it specifies the return shape (array), the exact fields included, and notes the documentation version (7.3.47 docs). It does not disclose potential pagination, rate limits, or error behavior, but for a read-only list operation with no parameters, the provided detail is strong.

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 a single, information-dense sentence that front-loads the core action ('List all link stations') and then enumerates the return fields. It is not overly verbose, but the field list is long and somewhat technical; it could be slightly more scannable with bullet points or a shorter summary. Still, every part earns its place by documenting the output structure.

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

Completeness4/5

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

Given the tool has no parameters, an output schema exists, and annotations cover safety, the description is largely complete. It details the return fields extensively, which is the main thing an agent needs to know. Minor gaps: it doesn't mention whether the list is sorted, whether it can be empty, or any error conditions, but these are not critical for a read-only list tool with no inputs.

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

Parameters4/5

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

The tool has zero parameters, so the schema is trivially complete (100% coverage). The description adds no parameter semantics because there are none to describe. Per the rubric, 0 params = baseline 4, and the description appropriately focuses on the return payload instead. It could theoretically mention that no arguments are required, but the empty schema already conveys that.

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 verb 'List' and the resource 'all link stations managed by UniFi Protect', which distinguishes it from sibling tools like protect_get_link_station (singular) and protect_list_cameras. It also specifies the return type (array) and enumerates the fields included, making the tool's purpose unambiguous.

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

Usage Guidelines4/5

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

The description implies usage context: it lists all link stations, contrasting with the singular get_link_station sibling. However, it does not explicitly state when to use this tool versus alternatives (e.g., 'use get_link_station for a single station'), nor does it mention any exclusions or prerequisites. The context is clear enough for an agent to infer the primary use case, but explicit routing guidance is absent.

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