Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_unpin_message

Unpins a specific Discord message by channel ID and message ID, removing it from the channel's pinned list; requires Manage Messages permission.

Instructions

Unpin 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_unpin_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdYesDiscord id (snowflake)
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 burden, and it does disclose the required permission. It omits other behavior an agent needs: what happens if the message is not currently pinned, whether the call is idempotent, and what failure modes occur without Manage Messages.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler, action front-loaded and the permission caveat immediately after. Nothing could be removed without losing information.

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 two-parameter mutation with no output schema, the definition covers the action and the permission prerequisite. It does not cover error or no-op behavior, which matters for an agent deciding whether to call it blindly.

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 coverage is 50% but the messageId $ref inherits the snowflake description, so both IDs are effectively documented in the schema. The description adds no meaning of its own about the parameters, so the baseline of 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?

States a specific verb and resource ('Unpin a message'), which is unambiguous against the sibling discord_pin_message. It does not explicitly name the inverse tool, but the distinction is inferable from the name and the stated action.

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 definition gives a prerequisite ('Requires Manage Messages') but no guidance on when to prefer this over alternatives such as deleting or editing a message. Usage context is implied by the name rather than explained.

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