Skip to main content
Glama

Create banned phrase group

filters_banphrases_create

Create a new empty banned phrase group so you can later add blocked phrases to a StreamElements chat filter.

Instructions

Create a new, empty banned phrase group. Add phrases to it afterwards with filters_banphrases_update.

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

Input Schema

NameRequiredDescriptionDefault
nameYesGroup name
channelNoStreamElements channel id (24-char hex). Defaults to SE_CHANNEL_ID or the channel that owns the token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false and openWorld=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: the group is created empty and requires a two-step workflow with filters_banphrases_update. It does not discuss permissions or the channel fallback behavior, keeping it short of a 5.

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 sentences, front-loaded with the core action and followed by the essential next step. Every sentence earns its place with no redundancy or filler.

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?

Given annotations and full schema coverage, the definition covers purpose and the two-step workflow. With no output schema, it does not say what the create call returns (e.g., an id needed to drive the follow-up update), which is a minor gap for an agent chaining calls.

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% — both the required name ("Group name") and the channel parameter, including its SE_CHANNEL_ID default, are documented in the schema. The description adds nothing beyond that, so the baseline 3 applies.

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 ("Create a new, empty banned phrase group") and adds the qualifier "empty," which tells the agent exactly what state the resource starts in. It also names the sibling filters_banphrases_update as the follow-up, so it is distinguishable from the other filters_* tools without opening a 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?

It gives clear context for when to use this tool — to create a new group — and explicitly routes the agent to filters_banphrases_update for the subsequent step of adding phrases. There is no explicit when-not guidance, but for a straightforward create operation the workflow direction is unambiguous.

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