Skip to main content
Glama

discord_pin_message

Pin or unpin messages in Discord channels to highlight important information or organize content.

Instructions

Pin or unpin a message in a channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
message_idYes
pinYestrue to pin, false to unpin.

Implementation Reference

  • Handler logic for discord_pin_message tool, fetching the channel and message, then pinning or unpinning based on input.
    case "discord_pin_message": {
      const channel = await getTextChannel(args.channel_id as string);
      const msg = await channel.messages.fetch(args.message_id as string);
      if (args.pin) { await msg.pin(); } else { await msg.unpin(); }
      return { content: [{ type: "text", text: `✅ Message ${args.pin ? "pinned" : "unpinned"}.` }] };
    }
  • Schema definition for discord_pin_message tool.
    {
      name: "discord_pin_message",
      description: "Pin or unpin a message in a channel.",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          message_id: { type: "string" },
          pin: { type: "boolean", description: "true to pin, false to unpin." },
        },
        required: ["channel_id", "message_id", "pin"],
      },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action but doesn't mention important behavioral aspects: whether pinning requires specific permissions, if there are limits on pinned messages per channel, what happens when unpinning, or error conditions. The description is minimal and lacks operational context.

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?

The description is extremely concise - a single sentence that directly states the tool's function with zero wasted words. It's front-loaded and gets straight to the point without unnecessary elaboration.

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

Completeness2/5

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

For a mutation tool (pinning/unpinning changes message state) with no annotations and no output schema, the description is insufficient. It doesn't cover behavioral aspects, error conditions, permissions needed, or what the tool returns. Given the complexity of Discord operations and lack of structured metadata, the description should provide more operational context.

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 only 33% (only the 'pin' parameter has a description). The description doesn't add any parameter semantics beyond what's in the schema - it doesn't explain what channel_id or message_id represent, how to obtain them, or format requirements. However, with 3 straightforward parameters and the pin parameter well-described in schema, baseline 3 is appropriate.

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?

The description clearly states the action ('Pin or unpin') and resource ('a message in a channel'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'discord_edit_message' or 'discord_delete_message' which also modify messages, missing an opportunity for clearer sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing appropriate permissions), when pinning is appropriate versus other message modifications, or how it relates to similar tools like editing or deleting messages in the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server