Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Follow announcement channel

follow_announcement_channel

Subscribe a target channel to an announcement channel so crossposted messages appear automatically. Use it to route update posts into the correct Discord channel.

Instructions

Subscribe a channel to an announcement channel, so crossposted messages from the source appear in the target.

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": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "follow_announcement_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoGuild (server) name or ID. Omit to use the default guild.
sourceYesAnnouncement channel name or ID to follow.
targetYesChannel where its posts should appear.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description is consistent with that: it creates a subscription rather than removing data. It adds useful context about the resulting behavior (crossposts land in the target), but omits required permissions, idempotency (what happens if already following), and whether an unfollow counterpart exists.

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 tight sentence with the action front-loaded and the consequence trailing, with no filler. Slightly awkward phrasing ('Subscribe a channel to an announcement channel') but nothing that needs cutting.

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?

For a 3-parameter mutation tool with no output schema and only minimal annotations, the description covers the core effect but leaves gaps an agent would care about: permission requirements, behavior when the follow already exists, and reversibility. Adequate but not complete.

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 100%, so all three parameters are already documented in the schema, including the guild fallback behavior. The description reinforces the source/target relationship but adds no format, ID-vs-name, or constraint detail beyond what the schema provides.

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?

States a specific verb ('Subscribe') and resource ('a channel to an announcement channel') and explains the resulting effect: crossposted messages from the source appear in the target. This disambiguates the source/target direction well, though it doesn't contrast itself with any sibling channel tool.

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?

Usage is implied by the described effect rather than stated: an agent can infer to call this when it wants posts mirrored into another channel. There is no explicit when-not guidance, no mention of prerequisites (e.g. the bot needing channel/webhook management rights), and no note about how to undo the follow.

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