Skip to main content
Glama
Sign In
better-discord-mcp

better-discord-mcp

by Sys0xdbg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

discord_remove_all_reactions

Remove all reactions from a Discord message, or specify an emoji to remove only that reaction.

Instructions

Remove all reactions (or all of one emoji) from a message.

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": {
      "channelId": "<channelId>",
      "messageId": "<messageId>"
    },
    "name": "discord_remove_all_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiNo
confirmNoSet true to actually perform this destructive action
channelIdYes
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description must carry full burden. It indicates destructive action ('remove') but does not disclose permissions needed, error cases, rate limits, or what happens to the message. Only basic transparency.

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?

Single sentence with no redundancy. Front-loaded with key action and scope. Every word earns its place.

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

Completeness2/5

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

For a destructive tool with no annotations and 4 params, the description is too brief. Does not explain confirm boolean necessity, return format, or failure modes. Leaves significant gaps for an agent.

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 has 4 params with 25% coverage (only confirm has description). Description adds emoji behavior context but ignores channelId, messageId, and confirm purpose. Fails to compensate for low schema coverage.

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?

Description clearly states verb 'remove', resource 'all reactions (or all of one emoji)', and object 'from a message'. Distinguishes from siblings like discord_remove_reaction and discord_remove_user_reaction.

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 guidance on when to use this tool vs. alternatives. Does not mention prerequisites, when to provide emoji vs. omit, or when to use other reaction tools. Implied usage is too vague.

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