Moderation API

wordlist-delete

Destructive

Delete wordlist

Delete a wordlist and its words. Channels that use the wordlist do not block the delete: the wordlist is removed from their policies. detachedChannelIds lists those channels. This cannot be undone.

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": {
      "request": "<request>"
    },
    "name": "wordlist-delete"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Beyond destructiveHint=true and idempotentHint=false, it discloses cascade behavior (words are deleted), a cross-resource side effect (channels are not blocked; the wordlist is stripped from their policies), the field naming that consequence (detachedChannelIds), and irreversibility. That is substantive operational context an agent cannot get from the annotations alone.

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?

Four short sentences, front-loaded with the action and scope, then side effects, then the irreversibility warning. Nothing is padded or repeated beyond the brief restatement of destruction that reinforces a critical warning.

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?

With no output schema, the description usefully supplies the response field detachedChannelIds and explains the policy side effect, which is the main thing an agent needs before a destructive call. It could still mention permission requirements or error cases (e.g. wordlist not found), but the essential picture is complete.

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 description coverage is reported at 0% for the single nested request object, and the description says nothing about `id` or about the `projectId` scoping rules (org-key vs project-key behavior). The narrative 100% ignores parameters, so it does not compensate for the coverage gap.

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?

"Delete a wordlist and its words" names a specific verb and resource and clarifies the scope is the whole wordlist, not individual entries, which separates it from sibling wordlist-words-remove. It stops short of naming that sibling explicitly, so the distinction must be inferred.

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

Usage Guidelines3/5

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

The description implies usage (whole-object removal, cascading to words) but never states when to choose this over wordlist-words-remove or wordlist-update. The channel-detachment note is behavioral context rather than selection guidance, and no prerequisites or exclusions are given.

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

All Moderation API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?