Skip to main content
Glama
owine

UniFi Protect MCP

by owine
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

protect_list_arm_profiles

Read-only

Lists all arm profiles from the local alarm manager, returning each profile's automations, schedules, activation delay, and creation details for review.

Instructions

List all arm profiles (only available when using the local alarm manager — the standalone NVR alarm system, not Protect cloud alerts). Returns array; each profile (7.1.83 docs): id, name, automations[], creator, schedules[], recordEverything, activationDelay (0 | 60000 | 300000 | 600000), createdAt, updatedAt.

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. Addedv2.10.0
  2. Removedv2.9.0
  3. Changed8 schema fields changedv2.7.5
    • addedOutput schema / properties / result / items / properties / activationDelay
      Added value: +{
+  "description": "Activation delay in ms: 0 | 60000 | 300000 | 600000 (number)"
+}
    • addedOutput schema / properties / result / items / properties / automations
      Added value: +{
+  "description": "Associated automation IDs (array of strings)"
+}
    • addedOutput schema / properties / result / items / properties / createdAt
      Added value: +{
+  "description": "Creation timestamp in epoch ms (number)"
+}
    • addedOutput schema / properties / result / items / properties / creator
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "ID of the user who created the profile"
+}
    • removedOutput schema / properties / result / items / properties / modelKey
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Resource kind"
-}
    • addedOutput schema / properties / result / items / properties / recordEverything
      Added value: +{
+  "description": "Record everything while active (boolean)"
+}
    • addedOutput schema / properties / result / items / properties / schedules
      Added value: +{
+  "description": "Arm schedules (array of objects)"
+}
    • addedOutput schema / properties / result / items / properties / updatedAt
      Added value: +{
+  "description": "Last update timestamp in epoch ms (number)"
+}
  4. 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 declare readOnlyHint=true and destructiveHint=false, indicating safe read. The description adds value by specifying the availability condition (local alarm manager) and the structure of the returned array, which goes beyond 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 a single sentence that packs essential info, but the inclusion of '7.1.83 docs' adds slight noise. Otherwise, it is front-loaded with the purpose and condition, making it efficient.

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?

Given the tool's simplicity (no parameters, read-only list), the description covers the necessary context: when to use, what it returns, and the field details. It lacks mention of empty result or error cases, but those are not critical for a basic list tool with good annotations.

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 no parameters, and schema coverage is effectively 100% (empty schema). Baseline for 0 parameters is 4, and the description does not need to add parameter information. It focuses on the output, which 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 clearly states the verb 'List' and the resource 'arm profiles', and distinguishes from siblings by specifying it's only available with the local alarm manager, not Protect cloud alerts. This makes the tool's purpose unambiguous and distinct from other list tools.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool (only when using the local alarm manager) and implicitly when not to use it (Protect cloud alerts). No alternative tool is mentioned, but the condition is clear enough to guide the agent.

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