Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

pin_message

Pins a message in a Discord channel using its channel ID and message ID, with an optional audit log reason.

Instructions

Pin a message in a channel. [PUT /channels/{channel_id}/messages/pins/{message_id}]

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

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
message_idYesMessage ID

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?

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the agent knows this mutates state without being destructive. The bracketed endpoint adds a hint of idempotent PUT semantics, but nothing is said about required permissions, per-channel pin caps, or what happens when a message is already pinned.

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 compact, front-loaded fragments with no wasted prose. The bracketed HTTP route is terse and marginally informative, though it is mostly redundant with the tool name.

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 simple three-parameter mutation tool with full schema coverage and safety annotations, the definition is minimally sufficient. It still leaves permission requirements and pin-limit behavior unstated, which an agent attempting the call would want to know.

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 three parameters (including the optional reason) are already documented in the schema, and the description adds nothing further about their meaning or format. Baseline 3 applies when the schema does the work.

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 and resource ('Pin a message in a channel'), which an agent can immediately distinguish from the sibling unpin_message and list_message_pins. It stops short of explicitly naming those siblings, so it is clear but not sharply differentiated.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as message permissions, and no reference to alternatives like list_message_pins for checking existing pins. Usage is only implied by the verb.

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