Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

bulk_leave_group_dms

Leave several Discord group DMs in one request by supplying channel IDs, so you can clean up multiple group conversations without leaving them individually.

Instructions

Leave several group DMs at once. [POST /users/@me/channels/bulk-leave]

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

Input Schema

NameRequiredDescriptionDefault
channel_idsYesChannel IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, but the description adds nothing beyond them. It does not say whether leaving is reversible, whether you can rejoin, what happens on partial failure with invalid channel IDs, or any rate-limit behavior — meaningful gaps for a mutation tool.

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?

Two short sentences with the action front-loaded; nothing is buried. The bracketed API path is marginal value that an agent rarely needs, keeping it just short of a 5.

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

Completeness3/5

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

For a one-parameter bulk mutation with annotations and no output schema, the essentials are present, but irreversibility and error/partial-success behavior are unaddressed. A caller still cannot predict what happens when some channel_ids are invalid.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents channel_ids fully. The description adds no format guidance (e.g., non-empty array, max batch size, whether IDs must be group DM channels), so baseline 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?

The description uses a specific verb and resource ('Leave several group DMs') with an explicit bulk scope, which distinguishes it from single-target siblings like leave_thread or leave_guild. It stops short of naming any sibling, so differentiation is inferred from the resource noun rather than stated.

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?

'At once' implies the batch case, but there is no explicit when-to-use, no when-not, and no pointer to an alternative for leaving a single group DM. An agent must infer the selection rule entirely from the phrase 'several group DMs'.

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