Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_crosspost_message

Idempotent

Publish an announcement message to all servers that follow the channel. Provide the announcement channel ID and message ID to crosspost it.

Instructions

Publish (crosspost) a message from an Announcement channel to every server that follows it. Only works in announcement channels on a message that has not already been published. Requires the Send Messages permission (and Manage Messages for messages authored by others). Returns a confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesID (snowflake) of the announcement channel containing the message.
message_idYesID of the message to publish to followers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / message_id / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed2 schema fields changedv1.6.0
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the announcement channel containing the message."
    • addedInput schema / properties / message_id / description
      Added value: +"ID of the message to publish to followers."
  4. Addedv1.5.0

TDQS

A4.5/5.0
Behavior5/5

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

Adds valuable behavioral context beyond the annotations: channel-type restriction, already-published precondition, permission nuances, and a returned confirmation. There is no direct contradiction with the annotations; the 'not already published' condition is a success precondition, not a claim about repeated side effects.

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?

Three front-loaded, purposeful sentences: action, key preconditions, permissions, and return. No filler, repetition, or unnecessary detail.

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?

Complete for a two-parameter tool with no output schema. It covers what the tool does, where it works, when it cannot work, what permissions are needed, and what the caller should expect as a result.

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?

The input schema already documents both snowflake parameters with 100% coverage. The description reinforces that channel_id must be an announcement channel and message_id is the message to publish, but adds no substantial new parameter-level meaning.

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 ('Publish (crosspost)') and resource ('a message from an Announcement channel to every server that follows it'). This clearly distinguishes the tool from regular sending, forwarding, or following operations among the sibling tools.

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

Usage Guidelines4/5

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

Provides clear conditions for use: announcement channels only, message must not already be published, and required permissions. It does not explicitly name an alternative tool for non-announcement-channel messages, so it stops just short of fully explicit routing guidance.

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