Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_saved_messages

Read-only

Retrieves your saved Discord messages, letting you review and access bookmarked content from your account.

Instructions

List your saved ("bookmarked") messages. [GET /users/@me/saved-messages]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_saved_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is fully covered by structured data. The description adds nothing beyond them—no indication of result limits, ordering, pagination, or whether it requires user auth—and the bracketed REST path is the only extra signal, mostly echoing the resource name.

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?

Two short clauses, front-loaded with the action and resource, with the parenthetical gloss and endpoint tag earning their space. Nothing redundant or padded.

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?

A zero-parameter read tool with no output schema is inherently simple, so the definition is close to sufficient. However, for a list endpoint the absence of any pagination or result-size hint is a real gap, since an agent cannot tell whether one call returns all saved messages or a page.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to clarify; baseline 4 applies. The description correctly implies no filtering or scoping options, consistent with the empty schema.

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?

States a specific verb and resource ('List your saved messages') and disambiguates the term by equating 'saved' with 'bookmarked', which is genuinely useful vocabulary. It does not distinguish itself from listing-like siblings such as search_messages or read_messages, keeping it at 4 rather than 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 guidance on when to use this versus search_messages or read_messages, and no mention of prerequisites, result volume, or pagination behavior. The agent must infer that this is the unfiltered 'show me everything I bookmarked' path from the name alone.

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