Skip to main content
Glama
owine

UniFi Protect MCP

by owine

protect_get_camera

Read-only

Get detailed information for a specific UniFi Protect camera by its ID. Returns camera name, MAC address, state, and settings.

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, activePatrolSlot, hasPackageCamera, hdrType, isMicEnabled, micVolume, videoMode, featureFlags, lcdMessage, ledSettings, osdSettings, smartDetectSettings) — there is no extended/by-id-only payload (confirmed live on 7.1.83). Recording state, motion events, zones, and channel/RTSP config are NOT exposed by this API surface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCamera ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoCamera ID
macNoMAC address
nameNoCamera name
stateNoCONNECTED | DISCONNECTED | ...
hdrTypeNoHDR mode, e.g. "auto"
modelKeyNoAlways "camera"
micVolumeNoMicrophone volume 0-100 (number)
videoModeNoVideo mode, e.g. "default"
lcdMessageNo
ledSettingsNo
osdSettingsNo
featureFlagsNo
isMicEnabledNoMicrophone enabled (boolean)
activePatrolSlotNoActive PTZ patrol slot, or null (number|null)
hasPackageCameraNoHas a secondary package camera (boolean)
smartDetectSettingsNo
Behavior5/5

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

Beyond readOnlyHint annotation, description lists exact fields returned and explicitly states what is NOT exposed (recording state, motion events, etc.), providing valuable behavioral context.

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?

Two well-structured sentences: first states purpose, second provides critical context and comparison. No extraneous information.

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?

Covers purpose, parameter, output fields, and limitations. With output schema present, description sufficiently completes the understanding for a simple get-by-id tool.

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?

Schema has 100% coverage with parameter description 'Camera ID'. Description adds no additional meaning or format details beyond 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?

Clearly states verb 'Get' and resource 'camera by ID'. Distinguishes from sibling protect_list_cameras by noting the same field set, no extended payload.

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?

Explicitly compares with protect_list_cameras, indicating when to use this tool (single camera) vs listing all cameras. Also implicitly distinguishes from other get tools by resource name.

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