Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

unpin_message

Destructive

Remove a pinned message from a Discord channel using its channel and message IDs; optionally include an audit-log reason.

Instructions

Unpin a message. [DELETE /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": "unpin_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

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the description's only added signal — the DELETE endpoint — merely restates the destructive nature. It says nothing about permission requirements, whether the call fails when the message is not pinned, audit-log side effects, or idempotency, which is a meaningful gap for a mutation tool.

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, front-loaded fragments with zero filler; the operation is stated first and the endpoint second. Slight redundancy in repeating channel_id/message_id, but nothing wasteful.

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 single-purpose mutation with a fully documented schema and rich annotations, the description is adequate. It still omits failure modes and permission context that an agent would want before issuing a destructive DELETE.

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%, with channel_id, message_id and reason all documented (including that reason appears in the audit log). The description adds no parameter meaning beyond echoing the same two IDs in the path template, so the baseline 3 applies.

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?

"Unpin a message" is a specific verb+resource pair, and the appended DELETE path confirms the exact operation and scope. It does not distinguish itself from siblings such as pin_message or list_message_pins, so an agent must infer the inverse relationship rather than read it.

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 guidance, no mention of prerequisites (e.g. needing the message to currently be pinned, or required permissions), and no routing to pin_message or list_message_pins. Usage is only implied by the word "unpin."

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