UniFi Protect MCP

Overview Schema Source Related Servers Discussions Admin

protect_get_camera

Read-only

Retrieve camera details by ID to access configuration fields such as name, state, video mode, and LED settings from UniFi Protect.

Instructions

Get details for a specific camera by ID. The Protect Integration API returns the SAME field set as protect_list_cameras entries (id, mac, name, modelKey, state, type, guid, activePatrolSlot, hasPackageCamera, hdrType, isMicEnabled, micVolume, videoMode, featureFlags, lcdMessage, ledSettings, osdSettings, smartDetectSettings) — there is no extended/by-id-only payload (confirmed live on 7.3.47). Recording state, motion events, zones, and channel/RTSP config are NOT exposed by this API surface.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Camera ID

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Camera 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	Camera name
`type`	No	Hardware model name, e.g. "UVC G6 Turret", "UP Chime PoE", "UNVR-PRO"
`state`	No	CONNECTED \| DISCONNECTED \| ...
`hdrType`	No	HDR mode, e.g. "auto"
`modelKey`	No	Always "camera"
`micVolume`	No	Microphone volume 0-100 (number)
`videoMode`	No	Video mode, e.g. "default"
`lcdMessage`	No
`ledSettings`	No
`osdSettings`	No
`featureFlags`	No
`isMicEnabled`	No	Microphone enabled (boolean)
`activePatrolSlot`	No	Active PTZ patrol slot, or null (number\|null)
`hasPackageCamera`	No	Has a secondary package camera (boolean)
`smartDetectSettings`	No

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

Changed18 schema fields changedv2.11.5Sep 13, 2026

removedOutput schema / properties / hdrType / anyOf

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

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

removedOutput schema / properties / lcdMessage / properties / text / anyOf

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

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

removedOutput schema / properties / lcdMessage / properties / type / anyOf

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

addedOutput schema / properties / lcdMessage / properties / type / 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 / osdSettings / properties / overlayLocation / anyOf

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

addedOutput schema / properties / osdSettings / properties / overlayLocation / 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"
+]
```

removedOutput schema / properties / videoMode / anyOf

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

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

Changed4 schema fields changedv2.7.5Jun 21, 2026

addedOutput schema / properties / lcdMessage / additionalProperties
```
Added value: +{}
```

removedOutput schema / properties / lcdMessage / description

Removed value: -"Doorbell LCD message (object; often empty {})"

addedOutput schema / properties / lcdMessage / properties

Added value: +{
+  "resetAt": {
+    "description": "Auto-reset timestamp in epoch ms, or null (number|null)"
+  },
+  "text": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "description": "Message text shown on the doorbell LCD"
+  },
+  "type": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "description": "Message type, e.g. \"CUSTOM_MESSAGE\", \"LEAVE_PACKAGE_AT_DOOR\", \"DO_NOT_DISTURB\""
+  }
+}

addedOutput schema / properties / lcdMessage / type
```
Added value: +"object"
```

First observedv2.7.4Jun 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark this as read-only and non-destructive. The description adds substantial behavioral context beyond annotations by enumerating the exact returned field set, confirming there is no hidden extended payload, and explicitly stating which common camera data is not available. This is valuable, non-redundant disclosure.

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

Conciseness5/5

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

The key purpose is front-loaded in the first sentence, and the rest of the description earns its place: the field enumeration sets expectations and the explicit exclusions prevent misuse. Despite the long field list, there is no filler.

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 simple single-parameter read-only getter with an output schema, this description is complete. It tells the agent what will be returned, what will not be returned, and confirms there is no hidden extra payload, making the tool safely callable without further investigation.

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 already documents the single 'id' parameter as 'Camera ID' with 100% coverage. The description only restates that lookup is by ID, adding no format, source, or usage detail beyond the schema.

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 opens with a specific verb and resource: 'Get details for a specific camera by ID.' It further distinguishes itself from protect_list_cameras by clarifying it returns the same field set and offers no extended by-id payload, so an agent can confidently tell them apart.

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 makes the primary use case clear: fetch details for one camera by ID. It also gives useful exclusions by stating recording state, motion events, zones, and channel/RTSP config are not exposed, though it does not explicitly name alternative tools for those needs.

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