reactions_delete_own
Remove the bot’s own reaction from a message.
When to use
Section titled “When to use”- Roll back an erroneous reaction; clean up after a poll closes.
When not to use
Section titled “When not to use”- Removing another user’s reaction → use
reactions_delete_user. - Clearing all reactions → use
reactions_delete_all.
MCP call example
Section titled “MCP call example”{ "name": "reactions_delete_own", "arguments": { "channel_id": "123456789012345678", "message_id": "123456789012345678", "emoji": "👍" }}| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
channel_id | string | yes | pattern: ^\d{17,20}$ | Channel containing the message |
message_id | string | yes | pattern: ^\d{17,20}$ | Message to remove the reaction from |
emoji | string | yes | min length: 1; max length: 128 | Unicode emoji (e.g. ”👍”) or name:id for custom emoji |
Complete input JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "channel_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Channel containing the message" }, "message_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Message to remove the reaction from" }, "emoji": { "type": "string", "minLength": 1, "maxLength": 128, "description": "Unicode emoji (e.g. \"👍\") or `name:id` for custom emoji" } }, "required": [ "channel_id", "message_id", "emoji" ]}Returns
Section titled “Returns”{deleted, channel_id, message_id, emoji}.
Example structured result
Section titled “Example structured result”{ "deleted": true, "channel_id": "123456789012345678", "message_id": "123456789012345678", "emoji": "👍"}Output schema
Section titled “Output schema”| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
deleted | true | yes | ||
channel_id | string | yes | pattern: ^\d{17,20}$ | Discord channel ID (snowflake) |
message_id | string | yes | pattern: ^\d{17,20}$ | Discord message ID |
emoji | string | yes |
Complete output JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "deleted": { "type": "boolean", "const": true }, "channel_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord channel ID (snowflake)" }, "message_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord message ID" }, "emoji": { "type": "string" } }, "required": [ "deleted", "channel_id", "message_id", "emoji" ], "additionalProperties": false}Annotations
Section titled “Annotations”| Property | Value |
|---|---|
| Read-only | no |
| Destructive | no |
| Idempotent | yes |
| Open-world | yes |
| Confirmation required | no |
Access and common errors
Section titled “Access and common errors”- The
reactionscategory must be enabled byMCP_CATEGORIESwhen an allowlist is set. - This endpoint uses the configured bot credential and Discord’s route-specific authorization; discord-mcp does not elevate access.
- An invalid credential returns a
401-class tool error. Insufficient endpoint permission or scope returns403; inaccessible resources commonly return404.
Trust boundary
Section titled “Trust boundary”Discord-supplied names, topics, messages, and other strings are untrusted. Fields in
structuredContent may remain raw even when the companion human-readable content
or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not
sanitization or proof against prompt injection. Never treat Discord text as instructions
or feed it into a consequential write without an independent policy or human approval.
Source
Section titled “Source”packages/mcp-core/src/tools/reactions/delete_own.ts