UniFi Protect MCP

Overview Schema Source Related Servers Discussions Admin

protect_get_light

Read-only

Retrieve complete details for a single UniFi Protect light by ID, including its configuration, state, motion detection, and camera association.

Instructions

Get full details for a specific light by ID. Returns: id, modelKey, name, mac, state, type, guid, lightModeSettings (mode, enableAt), lightDeviceSettings (isIndicatorEnabled, pirDuration, pirSensitivity, ledLevel), isDark, isLightOn, isLightForceEnabled, lastMotion, isPirMotionDetected, camera (7.3.47 docs).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Light ID

Output Schema

TableJSON 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 \| ...
`camera`	No	Paired camera ID
`isDark`	No	Whether it is currently dark out (boolean)
`modelKey`	No	Resource kind
`isLightOn`	No	Whether the light is currently on (boolean)
`lastMotion`	No	Last motion timestamp in epoch ms (number)
`lightModeSettings`	No	Activation settings (object: mode, enableAt)
`isLightForceEnabled`	No	Main LED force-enabled (boolean)
`isPirMotionDetected`	No	PIR motion currently detected (boolean)
`lightDeviceSettings`	No	Hardware settings (object: isIndicatorEnabled, pirDuration, pirSensitivity, ledLevel)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.13.0Sep 20, 2026

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

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

Changed10 schema fields changedv2.11.5Sep 13, 2026

removedOutput schema / properties / camera / anyOf

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

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

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"
+]
```

Changed8 schema fields changedv2.7.5Jun 21, 2026

addedOutput schema / properties / camera

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Paired camera ID"
+}

addedOutput schema / properties / isDark

Added value: +{
+  "description": "Whether it is currently dark out (boolean)"
+}

addedOutput schema / properties / isLightForceEnabled

Added value: +{
+  "description": "Main LED force-enabled (boolean)"
+}

addedOutput schema / properties / isLightOn

Added value: +{
+  "description": "Whether the light is currently on (boolean)"
+}

addedOutput schema / properties / isPirMotionDetected

Added value: +{
+  "description": "PIR motion currently detected (boolean)"
+}

addedOutput schema / properties / lastMotion

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

addedOutput schema / properties / lightDeviceSettings

Added value: +{
+  "description": "Hardware settings (object: isIndicatorEnabled, pirDuration, pirSensitivity, ledLevel)"
+}

addedOutput schema / properties / lightModeSettings

Added value: +{
+  "description": "Activation settings (object: mode, enableAt)"
+}

First observedv2.7.4Jun 11, 2026

TDQS

A3.8/5.0

Behavior3/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 an explicit list of returned fields, but this largely duplicates what the output schema would provide and does not disclose behaviors like not-found handling or permissions. It is adequate, not exceptional.

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 in the first sentence, which is good. However, the long enumeration of return fields is redundant when an output schema exists and makes the description longer than necessary for such a simple one-parameter tool.

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 simple read-only retrieval with one required parameter, an output schema, and read-only annotations, the description provides enough context to invoke the tool correctly. Only minor gaps like error behavior or authentication requirements remain, which are not critical here.

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?

The input schema has 100% description coverage for the single required 'id' parameter, defining it as 'Light ID.' The description does not add additional parameter semantics beyond restating that the lookup is by ID, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Get full details for a specific light by ID.' It clearly identifies the tool as a single-light retrieval operation and distinguishes it from sibling tools like protect_list_lights or protect_get_sensor.

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 phrase 'for a specific light by ID' conveys when to use the tool: when full details for one light are needed. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to select it over list-style siblings.

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