Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_list_pins

List pinned messages in a Discord channel to review important discussions. Provide the channel ID to retrieve them.

Instructions

List pinned messages in a channel.

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": {
      "channelId": "<channelId>"
    },
    "name": "discord_list_pins"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden and does little: it does not mention required permissions, that Discord caps pins at 50 per channel, or whether results include message author/timestamp/attachments. Only the read nature is implied by 'List'.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though efficiency here shades into thinness given how much the tool leaves unexplained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the only place an agent could learn permissions, result shape, or the 50-pin ceiling — and it covers none of them. For a simple read tool this is the main remaining gap.

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 100% — channelId is documented with type, snowflake pattern, and a description — so the schema is doing the explanatory work. The description adds only the implicit constraint that the channel must be one the bot can see, which is not stated explicitly.

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 (list) and resource (pinned messages) scoped to a channel, which distinguishes it plainly from siblings like discord_list_messages-adjacent tools, discord_list_reactions, and discord_list_threads. It stops short of naming any alternative, but the purpose itself is unambiguous.

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?

No indication of when to prefer this over other listing tools, no prerequisites (the bot needs View Channel access to read pins), and no note on whether this covers forum/thread pins. The agent must infer all of this.

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