Skip to main content
Glama

Delete banned phrase group

filters_banphrases_delete
DestructiveIdempotent

Delete a banned phrase group and all its phrases permanently by group ID to clear unwanted chat filters from a StreamElements channel.

Instructions

Permanently delete a banned phrase group and all of its phrases.

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": {
      "groupId": "<groupId>"
    },
    "name": "filters_banphrases_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoStreamElements channel id (24-char hex). Defaults to SE_CHANNEL_ID or the channel that owns the token.
groupIdYesBanned phrase group id (24-character hex id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so safety is covered. The description adds meaningful context beyond them: the effect is permanent and cascades to all child phrases, which the annotations alone do not convey. It stops short of stating permission requirements or irreversibility warnings.

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?

A single eleven-word sentence, front-loaded with the destructive verb and the cascade scope. Nothing is padded or repeated.

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?

For a two-parameter destructive delete with no output schema, annotations plus a 100%-documented schema plus this description cover nearly everything needed. The only unaddressed angle is what an operator should do instead when deletion is not intended.

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%, with both channel and groupId fully documented (format, default resolution). The description adds no parameter-level detail, so the baseline of 3 applies.

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

Purpose4/5

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

States a specific verb ('Permanently delete') and resource ('banned phrase group'), and clarifies the cascade to contained phrases. It does not explicitly contrast against siblings like filters_banphrases_update or filters_banphrases_create, but the delete semantics are unmistakable.

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 when-to-use guidance and no alternatives are named. An agent is not told that filters_banphrases_update might be the non-destructive option, nor when deletion is appropriate versus disabling a phrase.

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