Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by qungtai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_delete_pin

DestructiveIdempotent

Unpin a pinned message from a Discord channel or thread using its channel and message IDs. Returns a confirmation with the unpinned message and channel IDs.

Instructions

Unpin a pinned message from a channel or thread. To add a pin use discord_create_pin, and to list all current pinned messages use discord_list_pins. Returns a confirmation object with the unpinned message and channel IDs. Bot permissions it may need: View Channel, Pin Messages. Changes or removes existing Discord data without an approval prompt.

Input Schema

NameRequiredDescriptionDefault
reasonNoAudit log reason sent in the X-Audit-Log-Reason header (up to 512 characters)
channel_idYesID of the channel or thread that holds the message
message_idYesID of the message

Output Schema

NameRequiredDescriptionDefault
unpinnedYes
channel_idYesDiscord snowflake ID as a numeric string
message_idYesDiscord snowflake ID as a numeric string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.2
    • addedInput schema / properties / channel_id / description
      Added value: +"ID of the channel or thread that holds the message"
    • addedInput schema / properties / message_id / description
      Added value: +"ID of the message"
    • changedInput schema / properties / reason / description
      Previous value: -"Audit log reason"New value: +"Audit log reason sent in the X-Audit-Log-Reason header (up to 512 characters)"
    • addedOutput schema / properties / channel_id / description
      Added value: +"Discord snowflake ID as a numeric string"
    • addedOutput schema / properties / message_id / description
      Added value: +"Discord snowflake ID as a numeric string"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new context: the required bot permissions (View Channel, Pin Messages) and the warning that it changes data without an approval prompt. The only weak spot is the return-value sentence, which largely restates the output schema.

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?

Three tight, front-loaded sentences with the core action first and alternatives immediately after. The return-shape sentence is mildly redundant given an output schema exists, costing a little efficiency but nothing structural.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations, a full-coverage schema, and an output schema already present, the description fills the remaining gaps that matter: permission requirements, the lack of an approval prompt, and sibling routing. Nothing an agent needs to invoke this correctly is missing.

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 audit-log reason header, are already documented in the schema. The description adds no constraint, format, or edge-case meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Unpin a pinned message from a channel or thread') and explicitly names the two sibling tools that cover the add and list cases. An agent can distinguish this from discord_create_pin and discord_list_pins without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Routes the agent explicitly: use discord_create_pin to add a pin and discord_list_pins to enumerate existing pins. The condition selecting each alternative is stated rather than inferred, leaving no ambiguity about which tool to pick.

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