Skip to main content
Glama
discord-mcp

discord-mcp

messages_publish

Publish a reviewed Discord announcement draft to a channel, including text, embeds, files, polls, and Components V2, with one-time approval to prevent unintended sends.

Instructions

Purpose: Publish a composed announcement through your Discord bot: text, embeds, file uploads, polls, and Components V2.

When to use: Send the reviewed messages_compose draft to a channel.

Approval: First call returns a bounded draft review, payload_hash, and one-time approval_id. With MCP_DRY_RUN=false, approve with __confirm:true, the unchanged __confirm_hash and __confirm_id.

Returns: status, sent_count, and a link/readback receipt for every known sent part. partial or unverified is not completion; inspect receipts and channel history before preparing a fresh approval for missing parts. Never resend the whole draft after partial delivery.

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>"
    },
    "name": "messages_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttsNo
pollNo
filesNo
embedsNo
contentNo
__confirmNoAuthorize the exact payload supplied in this call after reviewing its summary.
channel_idYesChannel where the reviewed draft will be published
componentsNo
__confirm_idNoOne-time approval ID returned by the preceding preview; expires shortly.
__confirm_hashNoSHA-256 payload_hash returned by the preceding preview.
allowed_mentionsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.31.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say it is a non-idempotent, non-destructive, open-world write; the description goes far beyond that with a two-phase approval protocol (bounded draft review, payload_hash, one-time approval_id), the MCP_DRY_RUN=false gate, and the expiry of the approval token. It also discloses the partial-delivery failure mode ('partial or unverified is not completion') and forbids resending the whole draft, which is exactly the kind of operational behavior an agent cannot infer from structured fields.

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?

Labeled sections (Purpose / When to use / Approval / Returns) front-load the essentials and every sentence carries operational weight. The Returns sentence slightly duplicates what the output schema already provides, which keeps it short of perfect economy.

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?

For an 11-parameter, deeply nested, non-idempotent publish tool, the description covers the workflow, the approval handshake, and the recovery path after partial delivery. Return values are covered by the output schema, and payload field constraints are covered by the schema, so the remaining burden on the description is met.

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 only 36% across 11 parameters, so the description must compensate; it does explain the confirm triad semantics (__confirm, unchanged __confirm_hash, __confirm_id) and their one-time nature. However, it adds nothing about content, embeds, files, poll, components, allowed_mentions, or tts, leaving the bulk of the payload parameters to the JSON schema's patterns and limits.

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 and resource ('Publish a composed announcement through your Discord bot') and enumerates the payload kinds it accepts (text, embeds, file uploads, polls, Components V2). It also positions itself against the sibling that produces its input (messages_compose), so an agent can tell publish apart from compose without opening either schema.

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?

Explicit 'When to use: Send the reviewed messages_compose draft to a channel' gives a clear trigger condition and the prerequisite step. There is no explicit exclusion against other send-shaped siblings such as messages_send or messages_update, so the routing is clear but not exhaustive.

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