Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

save_message

Bookmark a Discord message for later retrieval by saving it with its channel ID and message ID, so you can revisit important content without searching again.

Instructions

Save (bookmark) a message for later. [PUT /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": "save_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
due_atNo
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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation/safety profile is covered. The description adds only the PUT endpoint path; it says nothing about idempotency when a message is already saved, required scopes, or what the response contains. With annotations carrying the safety burden, this is adequate but thin.

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?

One sentence plus the endpoint reference, with the core action front-loaded and zero filler. Nothing could be removed without losing information.

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 small 3-parameter mutation with no output schema, the definition covers the essentials of what it does, but the semantics of the optional due_at parameter and the behavior on repeat saves are left unaddressed. An agent could invoke it correctly for the basic case but would be guessing about due_at.

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 67%, so channel_id and message_id are documented in the schema and due_at at least has a type hint. The description adds no meaning beyond the schema — nowhere does it explain what setting due_at actually does for a bookmarked message, which is the only non-obvious parameter.

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 gives a specific verb plus resource ('Save (bookmark) a message') and even the underlying endpoint, so the action is unmistakable. It does not name the natural inverse sibling (unsave_message) or otherwise differentiate, which keeps it short of 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?

'for later' weakly implies the use case, but there is no explicit when-to-use, no prerequisite (e.g., message must be visible to the caller), and no mention of unsave_message for removal or how this differs from pin_message, which also preserves 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