Skip to main content
Glama

UniFi Protect: List PTZ Presets

unifi_protect_list_ptz_presets
Read-only

List a PTZ camera's saved preset positions and their slot numbers by camera ID; use for cameras reporting PTZ support.

Instructions

List a PTZ camera's saved preset positions, with the slot number each one lives at. Only meaningful for cameras reporting hasPtz: true in unifi_protect_list_cameras. There is no tool to MOVE a PTZ camera or run a patrol: those commands exist only on Ubiquiti's official Integration API (a separate X-API-KEY auth this server does not use), not on the private API this server wraps — presets are created and driven from the Protect app itself.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cameraId": "<cameraId>"
    },
    "name": "unifi_protect_list_ptz_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
cameraIdYesCamera id — the `id` from unifi_protect_list_cameras, a 24-character hex string. Not the camera's name and not its MAC address.

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.1/5.0
Behavior4/5

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

readOnlyHint=true already covers safety, and the description adds real context beyond that: this wraps a private API, not Ubiquiti's official Integration API, and move/patrol commands are unavailable here. It does not say what happens when the camera lacks PTZ (error vs. empty list), which keeps it short of a 5.

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 core action and the hasPtz precondition are front-loaded in the first two sentences. The final sentence on API/auth boundaries is long with parentheticals but still earns its place by stopping the agent from hunting for a move tool.

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?

For a one-parameter read tool with full schema coverage and no output schema, the description covers purpose, eligibility, and capability boundaries. The only gap is undefined behavior for a non-PTZ camera, which is minor.

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 coverage is 100% and the single cameraId parameter is fully documented in the schema (24-char hex id, not name or MAC). The description adds nothing about the parameter, so the baseline 3 applies.

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?

States a specific verb and resource ('List a PTZ camera's saved preset positions') plus the returned detail ('with the slot number each one lives at'). It also separates itself from sibling unifi_protect_list_ptz_patrols by clarifying that running patrols is out of scope, so an agent can route correctly without opening schemas.

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?

Gives an explicit precondition ('Only meaningful for cameras reporting hasPtz: true in unifi_protect_list_cameras'), which tells the agent both when to call it and how to verify eligibility. It also states what the server cannot do (move/patrol), though it names no alternative tool because none exists for this data.

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