Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

follow_channel

Follow a Discord announcement channel into a server channel so its posts mirror there; requires Manage Webhooks permission in the target channel.

Instructions

Follow an announcement channel into one of your server channels (needs Manage Webhooks there). [POST /channels/{channel_id}/followers]

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

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
webhook_channel_idYeswebhook channel id (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 profile is structured. The description adds a genuine behavioral fact the annotations do not carry: the Manage Webhooks permission requirement. It still omits the side effect that following implicitly creates a webhook in the target channel and causes messages to be relayed, and says nothing about idempotency or error behavior.

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 carries the action, the scope, and the permission requirement, followed by a short endpoint tag. Nothing is padded, though the bracketed endpoint is somewhat redundant for an agent that already has 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 full schema coverage, explicit annotations, and no output schema, most of the calling contract is already supplied. The remaining gap is behavioral: what following actually does (webhook creation, message relaying from the announcement channel) and what errors or preconditions apply beyond permission, which a mutation tool like this should still state.

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 already documented, giving a baseline of 3. The description adds some meaning by framing channel_id as the announcement channel being followed and webhook_channel_id as the destination server channel, which partially disambiguates the opaque 'webhook channel id' label, but it does not map either name explicitly to its role.

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?

Uses a specific verb ('Follow') plus a specific resource ('an announcement channel into one of your server channels') and even tags the underlying endpoint POST /channels/{channel_id}/followers. An agent can tell what the operation does without opening the schema. It does not explicitly contrast itself with any sibling (e.g., webhook or channel-creation tools), which keeps it below a 5.

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 parenthetical '(needs Manage Webhooks there)' gives a real prerequisite for use, which is useful context. However, there is no guidance on when to prefer this over alternatives such as list_channel_webhooks or create_guild_channel, no note on failure modes (already following, missing permission), and no when-not-use condition.

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