Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_message_pins

Read-only

Retrieve pinned messages from a Discord channel, newest pins first, with optional limit and before-time filters for finding key channel content.

Instructions

List pinned messages in a channel (newest pins first). [GET /channels/{channel_id}/messages/pins]

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>"
    },
    "name": "list_message_pins"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-50
beforeNoPins before this ISO time
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile needs no restating. The description contributes the result ordering ('newest pins first') and the underlying endpoint, which is genuine added context, but it says nothing about pagination behavior or what happens when a channel has no pins.

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?

One compact sentence plus a bracketed endpoint reference; the core purpose and ordering are front-loaded with no filler. The endpoint tag is marginally redundant but cheap and useful for mapping to the HTTP API.

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?

This is a simple read-only list tool with full schema documentation and no output schema, so the description need not explain return values. The only meaningful gap is that the description doesn't spell out how limit and before combine to page through results, which is minor given the schema text.

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 limit, before, and channel_id are already documented in the schema ('Pins before this ISO time', '1-50'). The description adds nothing about parameter interaction or how 'before' relates to the newest-first ordering, leaving 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?

States a specific verb (List) and resource (pinned messages in a channel) plus the ordering rule, which is enough to distinguish it from siblings like pin_message, unpin_message, and get_message without opening a schema. It does not explicitly name those siblings, so it falls short of the top score.

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?

Usage is implied by the resource name: an agent can infer this is the read path for pins. But there is no explicit when-to-use guidance, no pointer to the mutation siblings (pin_message/unpin_message), and no statement of prerequisites such as access to the channel.

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