Skip to main content
Glama

UniFi Protect: Get Event Thumbnails

unifi_protect_get_event_thumbnails
Read-only

Fetches still frames for up to six UniFi Protect events at once, returning them inline for vision inspection so you can identify who or what triggered motion events lacking smart detection.

Instructions

Fetch the still frames for SEVERAL events at once and return them inline to look at. This is the tool for answering who or what was actually there, and it matters most when a camera has no smart detection: motion events carry no classification, so the only way to tell a person from a branch is to look. Prefer this over calling unifi_protect_get_event_thumbnail repeatedly. Costs roughly 1-2K tokens per image, so it is capped at 6 — pick the events worth seeing from unifi_protect_list_events rather than sweeping a whole night. Events that have no thumbnail are reported by id instead of failing the call.

Input Schema

NameRequiredDescriptionDefault
outputNo"image" returns the frames inline for a vision model to look at, which is the point of this tool; "file" writes them to disk and returns paths instead.image
eventIdsYesEvent ids from unifi_protect_list_events, at most 6. Results showing `hasThumbnail: true` have an image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only carry readOnlyHint=true, and the description goes well beyond it: approximate token cost per image (~1-2K), a hard cap of 6, and graceful degradation ("Events that have no thumbnail are reported by id instead of failing the call"). Those are exactly the cost and failure-mode facts an agent needs before choosing batch size.

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?

Front-loaded with the verb and scope, and the alternative-routing comes before the cost warning. Slightly redundant — the 6-image cap and the "don't sweep all night" guidance are stated twice in adjacent sentences.

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?

With no output schema, the description still covers the return shape well (inline images vs file paths, id-only entries for missing thumbnails). What it doesn't say is how inline images and the by-id failure list are combined in the response, a minor gap for an agent parsing results.

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 description coverage is 100%, so baseline applies. The description's param-relevant content ("capped at 6", inline vs file) largely restates the schema's maxItems: 6 and the output enum description, adding only the pointer that ids come from list_events with hasThumbnail: true.

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?

Specific verb+resource ("Fetch the still frames for SEVERAL events at once and return them inline") with explicit plural scope that separates it from the singular sibling unifi_protect_get_event_thumbnail. It even names the downstream goal (telling a person from a branch), so the agent knows what the output is for.

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?

Gives an explicit alternative and preference ("Prefer this over calling unifi_protect_get_event_thumbnail repeatedly"), names the upstream source of ids (unifi_protect_list_events, filtered on hasThumbnail: true), and explicitly warns against bulk sweeps of a whole night.

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