MCP Discord Bot Server

discord_pin_message

Pin an existing Discord message in a channel using its channel ID and message ID; returns JSON confirmation.

Instructions

Pin a message in a Discord channel.

Args:
    channel_id: The ID of the channel containing the message.
    message_id: The ID of the message to pin.

Returns:
    JSON confirmation of the message being pinned.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`channel_id`	Yes	The ID of the Discord channel containing the message. Required.
`message_id`	Yes	The ID of the message to pin. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It only states the action and mentions a JSON return, but omits key behavioral details like required permissions, whether pinning is idempotent, the channel pin limit, or what happens if the message is already pinned.

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?

Front-loaded with a clear one-line purpose, then short Args and Returns sections. The Args and Returns duplicates the schema and output schema somewhat, but the description remains compact and well-structured overall.

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 tool with full schema coverage and an output schema, the description covers the basics. However, with no annotations, it should disclose more behavioral context such as permission requirements or side effects, which are currently 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 the schema already fully documents both parameters. The description merely repeats the schema text for channel_id and message_id without adding any syntax, format, or constraint details beyond what is already available.

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: 'Pin a message in a Discord channel.' This distinguishes it from sibling message tools like send, read, edit, delete, and search, though it does not explicitly name or contrast with any sibling.

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?

No guidance on when to use this tool versus alternatives, no prerequisites such as required permissions (e.g., MANAGE_MESSAGES), and no context for when pinning is appropriate or not.

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

Deploy Server