Skip to main content
Glama

unifi_gen_deletewifibroadcast

unifi_gen_deletewifibroadcast
DestructiveIdempotent

Deletes a UniFi WiFi broadcast by its ID, with preview/dry-run support and confirmation required to apply the removal.

Instructions

Delete Wifi Broadcast - generated from developer.ui.com/network/v11.0.97/deletewifibroadcast

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wifiBroadcastId": "<wifiBroadcastId>"
    },
    "name": "unifi_gen_deletewifibroadcast"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
confirmNo"YES" to apply; without it the tool returns a preview.
dry_runNotrue: preview only, nothing is sent.
wifiBroadcastIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is known. The description however omits the most consequential behavioral detail — that without confirm="YES" the call only previews — leaving a writer that might think a delete happened when it didn't.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short, but half the content is a documentation URL rather than an actionable statement. It is front-loaded on the action, though there is nothing of substance behind it.

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?

For a destructive mutation with no output schema, an undocumented half of the parameters, and a two-step preview/apply flow, the description should explain the confirmation gate and irreversibility. It explains neither.

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

Parameters2/5

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

Schema coverage is only 50% and the description compensates for none of it: the required wifiBroadcastId is undocumented here and 'force' has no type-independent meaning anywhere. The confirm/dry_run duplication is left to the schema as well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("Delete Wifi Broadcast"), so the core action is detectable, but the remainder is a provenance URL that adds no meaning and nothing distinguishes it from siblings like unifi_gen_deletenetwork or unifi_gen_deletevouchers.

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?

No indication of when to use this over alternatives, no prerequisites (e.g. that the ID must come from a get/list call), and no exclusions. The agent must infer everything from the name.

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

Deploy Server

Other Tools