Skip to main content
Glama
wowjinxy
by wowjinxy

pin_message

Pin important messages in Discord text channels to keep them visible and accessible for all members.

Instructions

Pin a message in a text channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
message_idYes
reasonNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'pin_message' tool. It fetches the specified channel and message, then pins the message using Discord's message.pin() method with an optional reason.
    async def pin_message(channel_id: str | int, message_id: str | int, reason: str | None = None, ctx: Context = None) -> str:  # type: ignore[override]
        """Pin a message in a text channel."""
    
        assert ctx is not None
        bot, _ = await _acquire(ctx)
        channel = await _ensure_channel(bot, _require_int(channel_id, "channel_id"))
        message = await _fetch_message(channel, _require_int(message_id, "message_id"))
        await _call_discord("pin message", message.pin(reason=reason))
        return f"Pinned message {message.id} in channel {channel.id}."
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 whether this requires specific permissions, what happens if the message is already pinned, rate limits, or what the output contains. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately front-loaded with the core action and resource, making it easy to parse quickly.

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?

Given this is a mutation tool with no annotations, 3 parameters at 0% schema coverage, but with an output schema present, the description is minimally adequate. The output schema will handle return values, but the description should do more to explain parameters, permissions, and behavioral context for a tool that modifies channel state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what 'channel_id' and 'message_id' refer to, their formats, or the optional 'reason' parameter's purpose. With 3 parameters completely undocumented, the description fails to provide meaningful semantic context beyond the basic action.

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') and resource ('a message in a text channel'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'unpin_message' beyond the opposite action, missing explicit differentiation that would warrant a perfect score.

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 like 'unpin_message' or other message management tools. There's no mention of prerequisites (e.g., needing appropriate permissions) or contextual cues for when pinning is appropriate versus other actions.

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/wowjinxy/mcp-discord'

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