UniFi Protect MCP

Overview Schema Source Related Servers Discussions Admin

Get link station

protect_get_link_station

Read-only

Retrieve full details for a specific non-alarm-hub UniFi Protect link station by ID, including state, LED settings, power, and Thread network status.

Instructions

Get full details for a specific link station by ID. Link stations are non-alarm-hub gateways (use protect_list_alarm_hubs for alarm hubs). Returns: id, modelKey ("linkstation"), name, mac, state, type, guid, isAlarmHub, ledSettings (isEnabled), lastEvent, alarmHub (armed, battery, buckboost, connector, cover, deviceTamperStatus (e.g. "tampered"), currentMeterChannelStatus, currentMeterStatus, inputPower, poeout, powerMeter, output and input (maps keyed by channel), inputTerminalStatus, outputTerminalStatus, emergencyTerminalStatus, auxiliaryPowerTerminalStatus), threadState (network: status, role, networkName, channel, panId, extendedPanId, joinedDeviceCount, errorReason, lastUpdatedAt) (7.3.70 docs).

Input Schema

Name	Required	Description	Default
`id`	Yes	Link station ID

Output Schema

Name	Required	Description
`id`	No	Device ID
`mac`	No	MAC address
`guid`	No	Hardware MODEL GUID, shared by every unit of the same model. NOT a per-device identifier — use `id` to identify a device.
`name`	No	Device name
`type`	No	Hardware model name, e.g. "UVC G6 Turret", "UP Chime PoE", "UNVR-PRO"
`state`	No	CONNECTED \| DISCONNECTED \| ...
`alarmHub`	No	Alarm hub status (object: armed, battery, buckboost, connector, cover, deviceTamperStatus (e.g. "tampered", added in 7.3.x), currentMeterChannelStatus, currentMeterStatus, inputPower, poeout, powerMeter, output and input (maps keyed by channel), inputTerminalStatus, outputTerminalStatus, emergencyTerminalStatus, auxiliaryPowerTerminalStatus)
`modelKey`	No	Resource kind
`lastEvent`	No	Last event timestamp in epoch ms (number)
`isAlarmHub`	No	Whether this device is an alarm hub (boolean)
`ledSettings`	No	LED settings (object: isEnabled)
`threadState`	No	Thread radio state, added in 7.3.x (object: network — status, role, networkName, channel, panId, extendedPanId, joinedDeviceCount, errorReason, lastUpdatedAt)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.15.0Oct 14, 2026

addedInput schema / properties / id / pattern
```
Added value: +"^[A-Za-z0-9_-]{1,64}$"
```
changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

changedOutput schema / properties / alarmHub / description

Previous value: -"Alarm hub status (object: armed, battery, connector, cover, output, input, …)"New value: +"Alarm hub status (object: armed, battery, buckboost, connector, cover, deviceTamperStatus (e.g. \"tampered\", added in 7.3.x), currentMeterChannelStatus, currentMeterStatus, inputPower, poeout, powerMeter, output and input (maps keyed by channel), inputTerminalStatus, outputTerminalStatus, emergencyTerminalStatus, auxiliaryPowerTerminalStatus)"

removedOutput schema / properties / deviceTamperStatus

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

Changed4 schema fields changedv2.13.0Sep 20, 2026

addedOutput schema / properties / deviceTamperStatus

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

addedOutput schema / 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 / 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 / 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 / mac / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / mac / type

Added value: +[
+  "string",
+  "null"
+]

removedOutput schema / properties / modelKey / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / modelKey / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / state / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / 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 / alarmHub

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

addedOutput schema / properties / isAlarmHub

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

addedOutput schema / properties / lastEvent

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

addedOutput schema / properties / ledSettings

Added value: +{
+  "description": "LED settings (object: isEnabled)"
+}

First observedv2.7.4Jun 11, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds value by enumerating the rich return payload (alarmHub fields, threadState, ledSettings), which is genuinely useful context beyond the annotations, but it does not discuss auth, rate limits, or failure modes.

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

Conciseness3/5

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

The first sentence is crisp and front-loaded, but the second sentence is an enormous field enumeration that repeats the output schema (which already exists per context signals) and is hard to scan. Much of that field list is redundant with the declared output schema and harms readability.

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?

For a single-param read tool with a declared output schema, the definition covers purpose, disambiguation, and return shape, so an agent can call it correctly. The verbatim field dump duplicates the output schema rather than adding explanation, leaving minor room to improve.

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?

Schema coverage is 100% and the single id parameter is fully documented with a pattern, so the schema already carries the semantics. The description reinforces that id is a 'link station ID' and disambiguates it from alarm-hub IDs, adding marginal value beyond the schema baseline of 3.

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?

States a specific verb (Get) and resource (link station) with scope (full details, by ID). It actively disambiguates from the sibling protect_get_alarm_hub by explicitly noting that link stations are non-alarm-hub gateways and routing alarm-hub callers to protect_list_alarm_hubs.

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 clearly establishes context by contrasting link stations with alarm hubs and pointing to protect_list_alarm_hubs for alarm hubs. However, it does not mention protect_list_link_stations as the way to discover IDs, and no explicit when-not-to-use condition is given beyond the alarm-hub exclusion.

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