Skip to main content
Glama
owine

UniFi Protect MCP

by owine
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

protect_list_cameras

Read-only

Retrieve all cameras managed by UniFi Protect with details on connection state, video modes, smart detection settings, LED and OSD configuration, and available feature flags.

Instructions

List all cameras managed by UniFi Protect. Returns array; each camera includes (Integration API 7.1.83-verified fields): id, mac, name, modelKey, state (CONNECTED/DISCONNECTED), activePatrolSlot, hasPackageCamera, hdrType, isMicEnabled, micVolume, videoMode, featureFlags (hasHdr, hasMic, hasSpeaker, hasLedStatus, smartDetectTypes[], smartDetectAudioTypes[], videoModes[], supportFullHdSnapshot), lcdMessage (type, resetAt, text), ledSettings (isEnabled, floodLed, welcomeLed), osdSettings (isNameEnabled, isDateEnabled, isLogoEnabled, isDebugEnabled, overlayLocation), smartDetectSettings (objectTypes[], audioTypes[]). The Integration API does NOT expose recording state, motion timestamps, connection/last-seen, firmware, host, or per-channel stream config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesArray of items returned by the list endpoint

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv2.7.5
    • addedOutput schema / properties / result / items / properties / lcdMessage / additionalProperties
      Added value: +{}
    • removedOutput schema / properties / result / items / properties / lcdMessage / description
      Removed value: -"Doorbell LCD message (object; often empty {})"
    • addedOutput schema / properties / result / items / 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 / result / items / properties / lcdMessage / type
      Added value: +"object"
  2. First observedv2.7.4

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds significant behavioral context by listing exactly which fields are returned and, importantly, what the API does NOT expose (recording state, motion timestamps, etc.), surpassing 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.

Conciseness4/5

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

The description is front-loaded with the purpose and then lists fields. While dense with information, it is not overly verbose. The field enumeration could be streamlined but remains clear and complete.

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?

Given zero parameters, a rich output schema (described in text), and full annotation coverage, the description provides complete context. It tells the agent exactly what to expect and what not to expect, with no gaps.

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?

There are zero parameters, and schema coverage is 100%. The description does not need to explain parameters; baseline is 4. No contradiction or missing info, but the description adds no parameter-specific value.

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 clearly states 'List all cameras managed by UniFi Protect', identifying the specific verb (list) and resource (cameras). It distinguishes from sibling list tools for other entities like protect_list_alarm_hubs, protect_list_bridges, etc.

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 provides clear context for when to use this tool (when listing cameras), but lacks explicit when-not-to-use or alternative references. Given siblings are all similarly named list tools for different entities, usage is implied but not explicitly guided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/owine/unifi-protect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server