Skip to main content
Glama

bulk_delete_hotspot_vouchers

Delete multiple UniFi hotspot vouchers in bulk by specifying host, site, and filter criteria. Remove unwanted vouchers matching your filters to keep your network organized.

Instructions

Bulk delete hotspot vouchers matching filter criteria.

host: console name, ID, or composite ID (MAC:numericId format). site: site name or ID. filter_params: filter parameters to select vouchers for deletion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYes
siteYes
filter_paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are available, so the description carries the full burden of behavioral disclosure. Despite being a destructive bulk operation, it does not warn that matching vouchers will be permanently deleted, mention irreversibility, or note any authorization requirements.

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 description is compact and front-loaded: the main purpose appears first, followed by brief parameter definitions. No filler is present, though the `filter_params` line is somewhat tautological.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is inadequate for a destructive bulk operation with no annotations and an opaque `filter_params` object. It omits irreversibility, criteria details, and any usage boundaries, even though an output schema exists and return-value explanation is not required.

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?

With 0% schema description coverage, the description must compensate. It usefully explains `host` as "console name, ID, or composite ID (MAC:numericId format)" and `site`, but `filter_params` is only described as "filter parameters," leaving the actual keys and value shapes undocumented.

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 states a specific verb and resource: "Bulk delete hotspot vouchers matching filter criteria." It distinguishes itself from the sibling `delete_hotspot_voucher` by emphasizing bulk operation and selection via filters, so an agent can tell it apart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no explicit when-to-use guidance or mention of alternatives like `delete_hotspot_voucher` for single deletions. The phrase "matching filter criteria" implies bulk selection, but no clear context or exclusions are provided.

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

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/swkstudios/unifi-fabric-mcp-server'

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