Skip to main content
Glama
Sign In
better-discord-mcp

better-discord-mcp

by Sys0xdbg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

discord_crosspost_message

Crosspost a message from an announcement channel to all followers. Provide the channel ID and message ID to publish.

Instructions

Publish (crosspost) a message from an announcement channel.

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": {
      "channelId": "<channelId>",
      "messageId": "<messageId>"
    },
    "name": "discord_crosspost_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdYes
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Without annotations, the description carries the full burden. It only states the basic function (crossposting) but does not disclose behavioral traits such as permissions required, whether it is reversible, rate limits, or the return value.

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, clear sentence with no unnecessary words. It is optimally concise and front-loaded.

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?

Given no annotations, no output schema, and minimal parameter info, the description is insufficient. It does not cover prerequisites, side effects, or return behavior, leaving significant gaps for an agent to use it correctly.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning to the parameters beyond their names ('channelId', 'messageId'). It does not explain formats, constraints, or how they relate to the 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 ('Publish (crosspost)') and the resource ('message from an announcement channel'). It is specific and distinct from sibling tools like discord_send_message or discord_edit_message, though it does not explicitly differentiate itself.

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 is provided on when to use this tool versus alternatives. It implies it's for announcement channels, but does not state when not to use it or mention any prerequisites or exclusions.

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