Skip to main content
Glama
ZenixSolutions

unifi-network-mcp

unifi_traffic_matching_lists

Destructive

Manage UniFi traffic matching lists with create, read, update, delete, and paginated list operations for classifying network traffic.

Instructions

Traffic matching lists. Operations:

  • list (Read): List Traffic Matching Lists

  • create (Create): Create Traffic Matching List

  • delete (Destructive): Delete Traffic Matching List — requires confirm: true

  • get (Read): Get Traffic Matching List

  • update (Update): Update Traffic Matching List List results are pages: { offset, limit (max 200), count, totalCount, data[] }. Filtering: pass filter as property.function(args); combine with and(...), or(...), not(...). Functions: eq, ne, gt, ge, lt, le, like, in, notIn, isNull, isNotNull; SET: contains, containsAny, containsAll, containsExactly, isEmpty. Strings use single quotes ('guest'); like patterns: '.'=one char, '*'=any run, ''=escape. For request-body shapes call unifi_spec with { operation: "unifi_traffic_matching_lists." }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoRequest body for: create, update. Exact schema via unifi_spec.
limitNoPage size (default 25, max 200). Used by: list.
filterNoFilter expression (see tool description). Used by: list.
offsetNoPagination offset (default 0). Used by: list.
siteIdNositeId (uuid). Used by: list, create, delete, get, update.
confirmNoMust be true to execute: delete. These change or remove live configuration.
consoleIdNoCloud mode only: the console to target. Discover IDs with unifi_consoles. Ignored in direct (single-console) mode.
operationYesWhich operation to perform.
trafficMatchingListIdNotrafficMatchingListId (uuid). Used by: delete, get, update.
Behavior4/5

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

Annotations already flag the tool as destructive (destructiveHint: true). The description adds valuable behavioral context: delete requires confirm: true, list results are paginated with specific fields, and the filter DSL is fully specified. This goes beyond what annotations provide, but it doesn't cover potential side effects of create/update or error behavior.

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?

Though lengthy, the description is well-structured and every section earns its place: operation list, pagination, filter DSL, and pointer to unifi_spec. It is front-loaded with the operation summary and then provides necessary details without fluff.

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?

The description thoroughly covers the list operation's response shape and the filtering system, and it tells agents how to get request-body schemas. However, it does not describe the return values for get/create/update/delete operations, and there is no output schema to fill that gap. This leaves some ambiguity for those operations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds substantial meaning beyond the schema: it explains the full filter expression grammar (functions, combinators, quoting, like patterns) and documents pagination semantics. It also clarifies that the body parameter for create/update should be retrieved via unifi_spec, which helps agents construct valid requests.

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 clearly states the resource ('Traffic matching lists') and enumerates specific operations (list, create, delete, get, update) with verbs. This distinguishes it from sibling tools that target different UniFi resources, and the operation list makes its scope immediately clear.

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?

It provides clear context for each sub-operation (read vs. destructive) and instructs that delete requires confirm: true. It also directs users to unifi_spec for request-body shapes, acting as a pointer for complex parameters. However, it does not explicitly mention when to use this tool over sibling tools, though that is reasonably implied by the resource-specific name.

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

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