Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_mentions

Read-only

Retrieve your recent Discord mentions and pings across servers, with optional filters for guild, role mentions, @everyone, limit, and pagination. Use it to review where you were mentioned.

Instructions

Your recent mentions inbox (pings across servers). [GET /users/@me/mentions]

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_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-100
rolesNoInclude role mentions
beforeNoReturn items before this ID (pagination)
everyoneNoInclude @everyone
guild_idNoServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 the safety profile is covered. The description adds that results are scoped to the current user across servers, which is genuinely useful scoping context, but it says nothing about ordering, recency window, or result volume beyond the word 'recent'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two terse fragments with the scoping qualifier front-loaded and no filler. The bracketed endpoint path is arguably redundant metadata but is compact and aids API mapping.

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 read-only list with five fully documented optional parameters, the description covers identity and scope adequately. With no output schema, however, it gives no indication of what a mention record contains or the default ordering, leaving an agent to discover the response shape by calling it.

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 all five parameters (limit, roles, everyone, before, guild_id) are already documented in the schema. The description adds no parameter meaning, such as how 'recent' interacts with the 'before' cursor or default ordering, so the baseline of 3 applies.

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 names a specific resource with scope: 'your recent mentions inbox (pings across servers)', which tells an agent this returns @-mentions for the authenticated user. It does not differentiate from any sibling tool or state the list verb explicitly, relying on the name for that, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Recent mentions inbox' implies the when-to-use context (retrieving pings directed at the user), but there is no explicit guidance, no exclusions, and no alternative tool named for adjacent needs. Usage is inferable but not stated.

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