Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

crosspost_message

Publishes an existing announcement-channel message to every server following that channel, extending its reach to subscribers.

Instructions

Publish a message in an announcement channel to all following servers. [POST /channels/{channel_id}/messages/{message_id}/crosspost]

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": {
      "channel_id": "<channel_id>",
      "message_id": "<message_id>"
    },
    "name": "crosspost_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
message_idYesMessage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation and open-world nature is known. The description adds genuinely useful behavior beyond that: the crosspost is broadcast to every following server, a fan-out effect worth knowing. It omits errors and limits, such as what happens if the message was already crossposted or is not in an announcement channel.

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?

A single front-loaded sentence states the action and its effect, followed by the endpoint mapping. Efficient, with only the bracketed route adding little for an agent that already knows the tool name.

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?

With just two required parameters, full schema coverage and no output schema, the definition covers what the tool does adequately. It is still thin for a public broadcast mutation: no permission requirements, no note that the source message must already exist in an announcement channel, and no mention of failure modes.

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 100%, so both parameters are documented and the baseline is 3. The description only marginally extends this by constraining channel_id to an announcement channel, and the schema's own note that channel_id may be a DM or voice channel is left un-reconciled with that constraint.

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 gives a specific verb and effect: publish an existing message in an announcement channel out to all following servers, which is clearly distinct from sending or replying to a message. It stops short of naming a sibling alternative, so the differentiation is inferential rather than explicit.

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 phrase 'in an announcement channel' implicitly scopes when this tool applies, and 'publish ... to all following servers' implies it operates on an already-sent message. However there is no explicit when-not guidance (e.g. use send_message instead to create a new post) and no stated prerequisites such as announcement-channel type or management permission.

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