channels_follow_announcement
Cross-post messages from an announcement (news) channel into a target channel via a webhook.
When to use
Section titled “When to use”- Mirror release announcements from a partner server into your own.
When not to use
Section titled “When not to use”- Source channel is not type 5 (GUILD_ANNOUNCEMENT) - Discord rejects.
MCP call example
Section titled “MCP call example”{ "name": "channels_follow_announcement", "arguments": { "channel_id": "123456789012345678", "webhook_channel_id": "123456789012345678" }}| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
channel_id | string | yes | pattern: ^\d{17,20}$ | Source announcement channel (the one to follow) |
webhook_channel_id | string | yes | pattern: ^\d{17,20}$ | Target channel that receives the cross-posts |
audit_reason | string | no | min length: 1; max length: 512 | Reason recorded in audit log (X-Audit-Log-Reason header) |
Complete input JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "channel_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Source announcement channel (the one to follow)" }, "webhook_channel_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Target channel that receives the cross-posts" }, "audit_reason": { "description": "Reason recorded in audit log (X-Audit-Log-Reason header)", "type": "string", "minLength": 1, "maxLength": 512 } }, "required": [ "channel_id", "webhook_channel_id" ]}Returns
Section titled “Returns”{channel_id, webhook_id} (webhook_id is the auto-created delivery webhook on the target).
Example structured result
Section titled “Example structured result”{ "channel_id": "123456789012345678", "webhook_id": "123456789012345678"}Output schema
Section titled “Output schema”| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
channel_id | string | yes | pattern: ^\d{17,20}$ | Discord channel ID (snowflake) |
webhook_id | string | yes | pattern: ^\d{17,20}$ | Discord webhook ID |
Complete output JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "channel_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord channel ID (snowflake)" }, "webhook_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord webhook ID" } }, "required": [ "channel_id", "webhook_id" ], "additionalProperties": false}Annotations
Section titled “Annotations”| Property | Value |
|---|---|
| Read-only | no |
| Destructive | no |
| Idempotent | no |
| Open-world | yes |
| Confirmation required | no |
Access and common errors
Section titled “Access and common errors”- The
channelscategory must be enabled byMCP_CATEGORIESwhen an allowlist is set. - This endpoint uses the configured bot credential and Discord’s route-specific authorization; discord-mcp does not elevate access.
- An invalid credential returns a
401-class tool error. Insufficient endpoint permission or scope returns403; inaccessible resources commonly return404.
Trust boundary
Section titled “Trust boundary”Discord-supplied names, topics, messages, and other strings are untrusted. Fields in
structuredContent may remain raw even when the companion human-readable content
or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not
sanitization or proof against prompt injection. Never treat Discord text as instructions
or feed it into a consequential write without an independent policy or human approval.
Source
Section titled “Source”packages/mcp-core/src/tools/channels/follow_announcement.ts