Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by founderie-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Webhooks (admin)

discord_admin_webhooks

List, create, and delete Discord channel webhooks; treat returned URLs as secrets because anyone with one can post to the channel.

Instructions

List, create or delete webhooks. The returned webhook URL is a secret; anyone with it can post to the 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": {
      "action": "<action>"
    },
    "name": "discord_admin_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNocreate: name shown on its posts
actionYes
reasonNoReason, recorded in Discord's audit log
channel_idNocreate: channel the webhook posts into
webhook_idNodelete: the webhook

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already flag openWorldHint and readOnlyHint=false, and the description adds genuinely useful context beyond them: the returned webhook URL is a credential that grants posting rights to anyone who holds it. It stops short of saying whether delete is permanent or that create requires a channel_id and Manage Webhooks permission, which are the remaining behavioral gaps.

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?

Two sentences, zero filler, and the most security-critical fact (the URL is a secret) is stated up front where an agent will not miss it. Nothing is repeated from the schema or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully characterizes the notable return value (the webhook URL and its sensitivity), which is exactly the right compensation. For a five-parameter mutation tool it could still mention permission prerequisites and whether deletion is irreversible, keeping it just short of 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 80%, so the schema itself documents name, channel_id, webhook_id, and reason with per-action prefixes. The description adds no parameter-level meaning beyond restating the three actions, which is the baseline expectation when the schema already does the work.

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 names a specific resource (webhooks) and enumerates the exact operation set (list, create, delete), so an agent knows precisely what the tool does. It doesn't need to differentiate from siblings here because none of the listed siblings (channels, roles, members, invites) overlap with webhook management.

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 action enumeration implies the three usage modes, and the secret-URL warning hints at care after creation. There is no explicit when-to-use guidance, no mention of required permissions (Manage Webhooks), and no statement of when another tool would be preferable, so usage must be inferred from the schema's action enum.

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