Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_all_reactions

Destructive

Remove every reaction from a Discord message using its channel and message ID. Requires Manage Messages permission.

Instructions

Remove every reaction from a message (needs Manage Messages). [DELETE /channels/{channel_id}/messages/{message_id}/reactions]

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_id": "<channel_id>",
      "message_id": "<message_id>"
    },
    "name": "remove_all_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
message_idYesMessage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The description explicitly states the scope ('Remove every reaction'), providing functional detail that complements the structural hints (destructiveHint: true). It clearly defines the tool's breadth of operation beyond simple safety classifications.

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?

The description is extremely concise, front-loading the primary action and immediate constraints. It avoids unnecessary filler, making it efficient and readable.

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

Completeness5/5

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

For a destructive operation like removing all reactions, the definition is complete. It covers the action, the target, and the necessary functional permissions, leaving no ambiguity for the agent.

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 coverage is 100%, meaning the input schema fully documents the required parameters. The description confirms the scope (channel and message ID) but adds no new semantic information beyond the provided structure, meeting the baseline score.

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 clearly identifies the resource (message reactions) and the precise action (Remove every reaction), distinguishing this tool from specific reaction removal functions.

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 provides a clear prerequisite ('needs Manage Messages'), informing the agent of the necessary capabilities to use the tool. This guidance helps qualify when the tool is appropriate for invocation.

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