Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_webhook

Creates a Discord channel webhook and returns its URL token so you can post messages through it.

Instructions

Create a webhook in a channel (returns its URL token). [POST /channels/{channel_id}/webhooks]

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

Input Schema

NameRequiredDescriptionDefault
nameYesName
avatarNo
reasonNoReason (shown in the audit log)
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 covered. The description adds real value with 'returns its URL token', warning the agent that a credential comes back, but it omits permission requirements and says nothing about rate limits or what happens on name collisions.

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?

One short sentence plus the endpoint route, front-loaded with the verb and the key return detail. Nothing is padded or repeated from the schema.

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 simple creation tool with no output schema, the definition covers the essential action and the notable return value. It falls short on prerequisites and the semantics of the required 'name' field, which an agent would need to call this correctly.

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 75%, so the schema carries most of the burden; the description adds no parameter meaning beyond it. Notably the schema's own description for 'name' is just 'Name', which neither structured field nor description clarifies (default name vs. unique constraint).

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 and resource plus scope: 'Create a webhook in a channel', and adds the notable side effect that a URL token is returned. This distinguishes it from modify_webhook and the non-webhook create_* siblings, though it does not name those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites (e.g. the permission needed to manage webhooks), and no pointer to the sibling tools for editing or deleting. An agent can infer the general intent from the verb, but nothing steers it between create_webhook and modify_webhook.

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