UniFi Network MCP Server

Overview Schema Source Related Servers Discussions Admin

List countries

unifi_list_countries

Read-only

List countries/regions and their ISO alpha-2 codes for building geo-IP firewall rules that match source or destination country. Use the code in firewall policies.

Instructions

List countries/regions (global) for geo-IP firewall rules. Returns: code (ISO alpha-2, e.g. 'US'), name. Use the code when building firewall policies that match by source/destination country.

Input Schema

Name	Required	Description
`limit`	No	Number of records to return (API default: 25)
`filter`	No	Filter expression (e.g., name.like('United*'))
`offset`	No	Number of records to skip

Output Schema

Name	Required	Description	Default
`data`	Yes
`count`	No
`limit`	No
`offset`	No
`totalCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.15.0Oct 14, 2026

changedInput schema / properties / limit / description

Previous value: -"Number of records to return (default: 25, max: 200)"New value: +"Number of records to return (API default: 25)"

changedInput schema / properties / offset / description

Previous value: -"Number of records to skip (default: 0)"New value: +"Number of records to skip"

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

Changed2 schema fields changedv2.13.0Sep 20, 2026

changedInput schema / properties / filter / description

Previous value: -"Filter expression (e.g., 'name.like(United*)')"New value: +"Filter expression (e.g., name.like('United*'))"

changedInput schema / properties / limit / minimum
```
Previous value: -1New value: +0
```

First observedv2.8.0Jun 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare this is a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), lowering the bar. The description adds that this is a global reference list (not tenant/site scoped) and enumerates the returned fields, which is useful behavioral context beyond the safety profile.

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, front-loaded with the purpose and scoping, followed by the practical usage tip. No filler or redundancy.

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?

An output schema exists so return values need not be re-explained, and annotations cover the safety profile. For a simple global reference-list tool, the description supplies everything needed to select and invoke it correctly.

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 limit, filter, and offset are already documented in the schema with examples. The description adds no parameter-level meaning, making the baseline 3 the correct score.

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 (List) plus resource (countries/regions) and scope qualifier (global, for geo-IP firewall rules), which cleanly separates it from site-scoped list siblings like unifi_list_firewall_zones or unifi_list_networks. An agent can tell what it returns (code/name) 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent to use the returned code when building firewall policies matching by source/destination country, which gives clear context for when the tool applies. It stops short of naming alternatives or exclusions, but for a static reference-list lookup the intended usage is fully conveyed.

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

Deploy Server