UniFi Protect MCP

Overview Schema Source Related Servers Discussions Admin

protect_list_sensors

Read-only

List all managed UniFi Protect sensors with details on state, type, battery, and detection flags. Enables monitoring of sensor health and activity at a glance.

Instructions

List all sensors managed by UniFi Protect. Returns array; each sensor includes: id, modelKey, name, mac, state, type, guid, mountType, featureFlags (temperature, humidity, light, motion, waterLeak, open, tamper, smoke — each {channelCount}), batteryStatus (percentage, isLow), stats (light, humidity, temperature), lightSettings, humiditySettings, temperatureSettings, isOpened, openStatusChangedAt, isMotionDetected, motionDetectedAt, motionSettings, glassBreakSettings, scheduleMode, armProfileIds, hasCustomSensitivityWhenArmed, alarmTriggeredAt, alarmSettings, leakDetectedAt, externalLeakDetectedAt, leakSettings, tamperingDetectedAt, wirelessConnectionState (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.

Changed3 schema fields changedv2.13.0Sep 20, 2026

addedOutput schema / properties / result / items / properties / featureFlags

Added value: +{
+  "description": "Sensor capability flags, added in 7.3.x (object: temperature, humidity, light, motion, waterLeak, open, tamper, smoke — each { channelCount })"
+}

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 / type

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

Changed12 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 / mountType / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / result / items / properties / mountType / 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 / scheduleMode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / result / items / properties / scheduleMode / 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"
+]
```

Changed22 schema fields changedv2.7.5Jun 21, 2026

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

addedOutput schema / properties / result / items / properties / alarmTriggeredAt

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

addedOutput schema / properties / result / items / properties / armProfileIds

Added value: +{
+  "description": "Arm profile IDs this sensor belongs to (array of strings)"
+}

addedOutput schema / properties / result / items / properties / batteryStatus

Added value: +{
+  "description": "Battery status (object: percentage, isLow)"
+}

addedOutput schema / properties / result / items / properties / externalLeakDetectedAt

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

addedOutput schema / properties / result / items / properties / glassBreakSettings
```
Added value: +{
+  "description": "Glass-break detection settings (object)"
+}
```
addedOutput schema / properties / result / items / properties / hasCustomSensitivityWhenArmed
```
Added value: +{
+  "description": "Custom armed sensitivity enabled (boolean)"
+}
```
addedOutput schema / properties / result / items / properties / humiditySettings
```
Added value: +{
+  "description": "Humidity threshold settings (object)"
+}
```
addedOutput schema / properties / result / items / properties / isMotionDetected
```
Added value: +{
+  "description": "Motion currently detected (boolean)"
+}
```

addedOutput schema / properties / result / items / properties / isOpened

Added value: +{
+  "description": "Open/close contact state (boolean)"
+}

addedOutput schema / properties / result / items / properties / leakDetectedAt

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

addedOutput schema / properties / result / items / properties / leakSettings
```
Added value: +{
+  "description": "Leak detection settings (object)"
+}
```
addedOutput schema / properties / result / items / properties / lightSettings
```
Added value: +{
+  "description": "Light threshold settings (object)"
+}
```

addedOutput schema / properties / result / items / properties / motionDetectedAt

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

addedOutput schema / properties / result / items / properties / motionSettings
```
Added value: +{
+  "description": "Motion detection settings (object)"
+}
```

addedOutput schema / properties / result / items / properties / mountType

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Mount type, e.g. \"door\", \"leak\", \"garage\""
+}

addedOutput schema / properties / result / items / properties / openStatusChangedAt

Added value: +{
+  "description": "Open-status change timestamp in epoch ms (number)"
+}

addedOutput schema / properties / result / items / properties / scheduleMode

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Schedule mode: \"always\" | \"when_armed\""
+}

addedOutput schema / properties / result / items / properties / stats

Added value: +{
+  "description": "Environmental stats (object: light, humidity, temperature)"
+}

addedOutput schema / properties / result / items / properties / tamperingDetectedAt

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

addedOutput schema / properties / result / items / properties / temperatureSettings
```
Added value: +{
+  "description": "Temperature threshold settings (object)"
+}
```

addedOutput schema / properties / result / items / properties / wirelessConnectionState

Added value: +{
+  "description": "Wireless link state (object: signalState, batteryStatus, bridge)"
+}

First observedv2.7.4Jun 11, 2026

TDQS

A4.1/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 the return type (array) and a detailed field enumeration, giving the agent concrete visibility into response contents beyond what annotations provide.

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 purpose is front-loaded and easy to parse, but the long comma-separated field inventory makes the description heavier than necessary, especially since an output schema exists. The information is relevant, but some trimming would improve conciseness.

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?

For a zero-parameter, read-only list operation with an output schema, the description fully covers scope, return type, and field details. Nothing an agent needs to invoke the tool correctly is missing.

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 and the schema covers 100% of the input surface, so there are no parameters for the description to explain. Baseline 4 applies.

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 ('List') and resource ('all sensors managed by UniFi Protect'), making its scope unambiguous. It is clearly distinct from sibling protect_get_sensor and other list tools.

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

Usage Guidelines3/5

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

The phrase 'List all sensors' implies the tool is for batch retrieval of the full sensor set, but it does not explicitly name alternatives such as protect_get_sensor for individual sensors or state when not to use it. Usage is implied rather than spelled out.

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