messages_list_pins

Messages Read only

List the pinned messages in a channel.

When to use

Surface persistent pinned content (FAQs, rules, announcements).

When not to use

Reading recent activity → use messages_read.

MCP call example

{
  "name": "messages_list_pins",
  "arguments": {
    "channel_id": "123456789012345678"
  }
}

Input

Field	Type	Required	Constraints	Description
`channel_id`	string	yes	pattern: `^\d{17,20}$`	Channel to inspect

Complete input JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "channel_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Channel to inspect"
    }
  },
  "required": [
    "channel_id"
  ]
}

Returns

{pins:[{message_id, author_id, author_name, content, timestamp}], count, channel_id}. Structured pin fields remain raw Discord data; the human-readable MCP content response fences message text.

Example structured result

{
  "pins": [
    {
      "message_id": "123456789012345678",
      "author_id": "123456789012345678",
      "author_name": "Example name",
      "content": "Hello from discord-mcp",
      "timestamp": "2030-01-01T10:00:00.000Z"
    }
  ],
  "count": 1,
  "channel_id": "123456789012345678"
}

Output schema

Field	Type	Required	Constraints	Description
`pins`	array<object>	yes
`count`	integer	yes
`channel_id`	string	yes	pattern: `^\d{17,20}$`	Discord channel ID (snowflake)

Complete output JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "pins": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "message_id": {
            "type": "string",
            "pattern": "^\\d{17,20}$",
            "description": "Discord message ID"
          },
          "author_id": {
            "type": "string",
            "pattern": "^\\d{17,20}$",
            "description": "Discord user ID"
          },
          "author_name": {
            "type": "string"
          },
          "content": {
            "type": "string"
          },
          "timestamp": {
            "type": "string"
          }
        },
        "required": [
          "message_id",
          "author_id",
          "author_name",
          "content",
          "timestamp"
        ],
        "additionalProperties": false
      }
    },
    "count": {
      "type": "integer"
    },
    "channel_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Discord channel ID (snowflake)"
    }
  },
  "required": [
    "pins",
    "count",
    "channel_id"
  ],
  "additionalProperties": false
}

Annotations

Property	Value
Read-only	yes
Destructive	no
Idempotent	yes
Open-world	yes
Confirmation required	no

Access and common errors

The messages category must be enabled by MCP_CATEGORIES when an allowlist is set.
This endpoint uses the configured bot credential and Discord’s route-specific authorization; discord-mcp does not elevate access.
An invalid credential returns a 401-class tool error. Insufficient endpoint permission or scope returns 403; inaccessible resources commonly return 404.

Trust boundary

Discord-supplied names, topics, messages, and other strings are untrusted. Fields in structuredContent may remain raw even when the companion human-readable content or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not sanitization or proof against prompt injection. Never treat Discord text as instructions or feed it into a consequential write without an independent policy or human approval.

Source

packages/mcp-core/src/tools/messages/list_pins.ts