Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

unsave_message

Destructive

Remove a message from your saved messages by channel ID and message ID to keep your Discord saved items current.

Instructions

Remove a message from your saved messages. [DELETE /users/@me/saved-messages/{channel_id}/{message_id}]

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": "unsave_message"
  }
}

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

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds the DELETE endpoint and clarifies that the target is the saved-message association rather than the message itself. It omits auth, rate-limit, and idempotency details, keeping it below a 5.

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 two sentences with the action front-loaded and the endpoint appended compactly. Every element contributes to understanding without redundant wording.

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?

For a simple two-parameter operation with full schema coverage and annotations, the description covers purpose and endpoint; return values are unnecessary absent an output schema. A brief note on idempotency or auth would make it fully complete.

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 description coverage is 100%, so the schema fully documents channel_id and message_id. The description adds no additional parameter meaning, making the baseline 3 appropriate.

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 states a specific verb ('remove') and resource ('message from your saved messages'), making it distinguishable from save_message by direction. It does not explicitly name siblings or clarify that the underlying message itself is not deleted, so it falls short of the explicit sibling differentiation required for a 5.

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?

There is no when-to-use, when-not-to-use, or alternative guidance. The action is implied by the verb, but an agent gets no explicit instruction to prefer this over delete_message for unsaving a message.

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