UniFi Protect MCP

Overview Schema Source Related Servers Discussions Admin

Get light

protect_get_light

Read-only

Retrieve full details for a specific UniFi Protect light by ID, including settings, status, motion detection, and linked camera info.

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.70 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.15.0Oct 14, 2026
- addedInput schema / properties / id / pattern
```
Added value: +"^[A-Za-z0-9_-]{1,64}$"
```
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered without the description. The description adds nothing behavioral beyond that (no auth scope, error behavior, or freshness semantics), and its enumerated field list largely duplicates the output schema.

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?

Purpose is correctly front-loaded in the first clause, but the long inline enumeration of return fields and the trailing '(7.3.70 docs)' citation consume most of the text without aiding tool selection. Since an output schema already exists, that field list is redundant rather than informative.

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-parameter, read-only fetch with a full output schema and clear annotations, the description covers what an agent needs in order to call the tool correctly. The only missing piece is routing context against the list/get sibling pair.

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% and the single 'id' parameter is documented in the schema with a pattern constraint. The description restates only that lookup is 'by ID' and adds no format, uniqueness, or sourcing detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Get) and resource (light) with clear scope ('full details ... by ID'), distinguishing a single-item fetch from the sibling list tool protect_list_lights by implication. It does not explicitly name that sibling, so an agent must infer the retrieve-one vs enumerate-many split from naming convention.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus protect_list_lights or the broader family of protect_get_* tools, and no stated prerequisite such as needing an ID obtained from a list call. The 'by ID' phrasing only weakly implies the lookup flow.

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