Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_pin_message

Pins a Discord message in a specified channel, requiring Manage Messages permission, to highlight important content for server members.

Instructions

Pin a message. Requires Manage Messages.

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

Input Schema

NameRequiredDescriptionDefault
channelIdYesDiscord id (snowflake)
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the required permission (Manage Messages), which is genuinely useful context. It does not say whether the call is idempotent when a message is already pinned, whether the target message must exist, or what limits apply to the channel's pin set.

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 short sentences with the action front-loaded and zero filler. The sizing is appropriate for a simple two-parameter operation, though the permission note could have been merged into a richer single statement.

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 low-complexity mutation with no annotations and no output schema, the description covers the action and the permission requirement, which is the minimum an agent needs to attempt the call. It leaves out behavioral effects (already-pinned handling, failure modes), and those gaps matter more because nothing else supplies them.

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

Parameters2/5

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

Schema coverage is 50% – channelId carries a description (snowflake id) while messageId only refs it – and the description adds no parameter meaning at all. It neither explains which channel must contain the message nor clarifies the snowflake format, so it fails to compensate for the coverage gap.

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?

"Pin a message" states a specific verb and resource, which cleanly separates it from discord_unpin_message and other message tools. It stops short of naming the sibling alternative or the scope (channel), but an agent can identify the operation immediately.

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?

The description names a prerequisite (Manage Messages) but gives no guidance on when to choose this over discord_unpin_message or how it relates to message retrieval/editing. Usage is implied by the verb rather than 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