Skip to main content
Glama
mgcrea
by mgcrea

UniFi: List Clients

unifi_list_clients
Read-only

List the devices currently connected to a UniFi site. Filter by name, connection type, or connected-since time to retrieve only the active clients you need, each with its ID for follow-up actions.

Instructions

List the clients currently connected to a site — the devices on your network right now, not the historical list. Each entry carries the client id (a UUID the other client tools take), its name, type, IP, MAC and when it connected. Filtering happens on the console, so a filtered call is cheaper than reading pages and discarding them here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoMatch the client name, with `*` as a wildcard — e.g. "*iphone*".
siteNoWhich site to act on. Accepts the site UUID, its `internalReference` (the legacy 8-character name, usually "default") or its display name ("Default") — all three are resolved for you, so a guess costs nothing. Defaults to UNIFI_SITE, or to the only site when this console has just one. `unifi_list_sites` shows all three for every site.
typeNoConnection type to filter by. Omit for all types.
limitNoMaximum items to return (1-200; the console rejects more). Defaults to UNIFI_PAGE_LIMIT (50). Prefer narrowing with `filter` over raising this — the console filters server-side, so a filtered request is both smaller and faster than a large page read here.
filterNoRaw server-side filter expression, applied by the console before it answers — much cheaper than fetching pages and filtering here. Syntax: `property.function(value)`, combined with `and(...)`, `or(...)` and `not(...)`. Strings take single quotes (double an embedded quote to escape it); `*` is the wildcard in `like`. Functions: eq, ne, gt, ge, lt, le, like, in, notIn, isNull, isNotNull, contains, containsAny, containsAll. Examples: `state.eq('OFFLINE')`, `firmwareUpdatable.eq(true)`, `and(type.eq('WIRED'),name.like('*lab*'))`. The structured arguments on this tool build the common expressions for you — use this only for what they cannot express, and do not pass both.
connectedSinceNoOnly clients connected at or after this ISO 8601 timestamp, e.g. "2026-08-30T00:00:00Z".
Behavior4/5

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

The readOnlyHint annotation already signals safety, and the description adds useful behavioral context: this is a live snapshot, not history, and filtering is performed on the console for cost efficiency. It does not cover rate limits or auth, but the annotation plus the cost-oriented note are sufficient for this read-only listing tool.

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?

Three dense sentences with no filler. The core scoping is front-loaded, the output fields are summarized, and the filtering cost behavior is stated in one efficient sentence. Every sentence earns its place.

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 partially covers the return shape by listing the fields each entry carries. The rich parameter schema handles invocation details, and the filtering behavior is explained. Exact pagination or response envelope details are not stated, but for an optional-parameter list tool this is nearly complete.

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 the schema already documents every parameter well. The description adds general context about server-side filtering and mention of the client id being reused by other tools, but it does not need to repeat per-parameter semantics. Baseline 3 is appropriate.

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 uses a specific verb and resource: 'List the clients currently connected to a site', and adds a clear distinction from the historical list. It also identifies what each entry contains, making the tool's purpose unambiguous and distinct from unifi_get_client and unifi_list_devices.

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?

The description clearly frames when this tool is appropriate: for current network clients, not historical records, and it notes that server-side filtering is cheaper than fetching pages and discarding data. It does not explicitly name sibling alternatives and when to prefer them, but the context is strong enough for an agent to route correctly.

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/mgcrea/mcp-unifi-network'

If you have feedback or need assistance with the MCP directory API, please join our Discord server