Skip to main content
Glama
owine

UniFi Protect MCP

by owine
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

protect_list_speakers

Read-only

Retrieve all speakers managed by UniFi Protect, including their ID, name, status, volume, and microphone state.

Instructions

List all speakers managed by UniFi Protect. Returns array; each speaker includes: id, modelKey, name, mac, state, volume, micVolume, isMicEnabled, speakerState (status, mode), featureFlags (hasMic) (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. Addedv2.10.0
  2. Removedv2.9.0
  3. Changed5 schema fields changedv2.7.5
    • addedOutput schema / properties / result / items / properties / featureFlags
      Added value: +{
+  "description": "Feature flags (object: hasMic)"
+}
    • addedOutput schema / properties / result / items / properties / isMicEnabled
      Added value: +{
+  "description": "Microphone enabled (boolean)"
+}
    • addedOutput schema / properties / result / items / properties / micVolume
      Added value: +{
+  "description": "Microphone volume (number)"
+}
    • addedOutput schema / properties / result / items / properties / speakerState
      Added value: +{
+  "description": "Speaker state (object: status, mode)"
+}
    • addedOutput schema / properties / result / items / properties / volume
      Added value: +{
+  "description": "Speaker volume (number)"
+}
  4. First observedv2.7.4

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context (returns array, lists specific fields like state, volume) but does not go beyond what annotations and output schema suggest.

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 very concise: two sentences with no wasted words. It front-loads the main action then details outputs.

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, rich annotations, and an output schema (though not shown, the description lists fields), the description is complete for a simple list operation.

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?

Input schema has zero parameters, so parameter semantics are irrelevant. Baseline of 4 applies as the description does not need to compensate.

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 states it lists all speakers managed by UniFi Protect, with specific fields listed. It clearly distinguishes from sibling tools (e.g., protect_list_cameras) by indicating the resource type (speakers).

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

Usage Guidelines3/5

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

The description implies usage (when you need speakers list) but does not explicitly state when to use it over alternatives or when not to use it. No comparison with sibling tools provided.

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