UniFi Protect MCP

by owine

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get ULP user

protect_get_ulp_user

Read-only

Fetch details of a UniFi Identity (ULP) user by ID, returning full name, email, and status.

Instructions

Get details for a specific UniFi Identity (ULP) user by ID. Returns: id, modelKey, firstName, lastName, fullName, email, status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	ULP user ID

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	ULP user UUID
`email`	No	Email address, added in 7.3.x. Empty string for service accounts (verified live 7.3.70)
`status`	No	Account status, e.g. ACTIVE
`fullName`	No	Full name
`lastName`	No	Last name
`modelKey`	No	Always "ulpUser"
`firstName`	No	First name

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.15.0Oct 14, 2026

addedInput schema / properties / id / pattern
```
Added value: +"^[A-Za-z0-9_-]{1,64}$"
```
changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

changedOutput schema / properties / email / description

Previous value: -"Email address, added in 7.3.x. Empty string for service accounts (verified live 7.3.47)"New value: +"Email address, added in 7.3.x. Empty string for service accounts (verified live 7.3.70)"

Changed1 schema field changedv2.13.0Sep 20, 2026

addedOutput schema / properties / email

Added value: +{
+  "description": "Email address, added in 7.3.x. Empty string for service accounts (verified live 7.3.47)",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed10 schema fields changedv2.11.5Sep 13, 2026

removedOutput schema / properties / firstName / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / firstName / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / fullName / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / fullName / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / lastName / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / lastName / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / modelKey / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / modelKey / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / status / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / status / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedv2.7.4Jun 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description contributes the returned field list, but says nothing about auth requirements, error behavior for an unknown ID, or pagination concerns — acceptable but not rich.

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 tight sentences, zero filler, with the identity/scope qualifier front-loaded before the return-value enumeration.

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?

For a single-parameter read tool with full schema coverage, safety annotations, and an output schema, nothing an agent needs in order to call it correctly is missing.

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% and the single 'id' parameter carries its pattern and description in the schema, so the description's 'by ID' adds no syntax or format detail. Baseline 3 for a fully documented single parameter.

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 (Get) and resource (UniFi Identity/ULP user), qualified by ID lookup, which cleanly separates it from protect_list_ulp_users and from the similarly named protect_get_user. An agent can pick this tool without opening the schema.

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?

Usage is implied by 'by ID' — you call it when you already hold a ULP user ID — but the description never states when to prefer this over protect_list_ulp_users or protect_get_user, nor any prerequisites. Adequate but with an obvious routing gap.

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