Skip to main content
Glama
owine

UniFi Protect MCP

by owine
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

protect_list_lights

Read-only

Lists all lights managed by UniFi Protect with current state, mode settings, motion status, and camera details.

Instructions

List all lights managed by UniFi Protect. Returns array; each light includes: id, modelKey, name, mac, state, lightModeSettings (mode, enableAt), lightDeviceSettings (isIndicatorEnabled, pirDuration, pirSensitivity, ledLevel), isDark, isLightOn, isLightForceEnabled, lastMotion, isPirMotionDetected, camera (7.1.83 docs).

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. Changed8 schema fields changedv2.7.5
    • addedOutput schema / properties / result / items / properties / camera
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Paired camera ID"
+}
    • addedOutput schema / properties / result / items / properties / isDark
      Added value: +{
+  "description": "Whether it is currently dark out (boolean)"
+}
    • addedOutput schema / properties / result / items / properties / isLightForceEnabled
      Added value: +{
+  "description": "Main LED force-enabled (boolean)"
+}
    • addedOutput schema / properties / result / items / properties / isLightOn
      Added value: +{
+  "description": "Whether the light is currently on (boolean)"
+}
    • addedOutput schema / properties / result / items / properties / isPirMotionDetected
      Added value: +{
+  "description": "PIR motion currently detected (boolean)"
+}
    • addedOutput schema / properties / result / items / properties / lastMotion
      Added value: +{
+  "description": "Last motion timestamp in epoch ms (number)"
+}
    • addedOutput schema / properties / result / items / properties / lightDeviceSettings
      Added value: +{
+  "description": "Hardware settings (object: isIndicatorEnabled, pirDuration, pirSensitivity, ledLevel)"
+}
    • addedOutput schema / properties / result / items / properties / lightModeSettings
      Added value: +{
+  "description": "Activation settings (object: mode, enableAt)"
+}
  2. First observedv2.7.4

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnly and non-destructive behavior. The description adds value by detailing the return structure (array of lights with specific fields) and version reference, going beyond annotations.

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 description is concise with a single sentence stating purpose followed by a structured list of fields. Every sentence serves a purpose and is front-loaded.

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 the tool's simplicity (no parameters, simple list), the description fully covers the operation: it lists all lights and enumerates return fields. Output schema is effectively described.

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?

No parameters exist (0 params), so baseline 4 applies. The description adds no parameter information but compensates by describing output fields.

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 explicitly states 'List all lights' with a specific verb and resource, distinguishing from sibling 'protect_get_light' for single light retrieval.

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 that this tool lists all lights, implicitly suggesting use for bulk retrieval. However, it does not explicitly mention when not to use or name alternatives.

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