Skip to main content
Glama

discord_create_webhook

Create a webhook in a Discord channel to automate message delivery and integrate external services.

Instructions

Create a webhook on a channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
nameYesName for the webhook.
avatarNoOptional avatar URL for the webhook.

Implementation Reference

  • The handler logic for 'discord_create_webhook' which fetches the channel, checks for webhook support, and creates the webhook.
    case "discord_create_webhook": {
      const channel = await discord.channels.fetch(validateId(args.channel_id, "channel_id"));
      if (!channel || !("createWebhook" in channel)) throw new Error("Channel does not support webhooks.");
      const webhook = await (channel as any).createWebhook({
        name: args.name as string,
        avatar: (args.avatar as string | undefined) ?? undefined,
      });
      return {
        content: [{
          type: "text",
          text: `✅ Webhook "${webhook.name}" created (id: ${webhook.id}, token: ${webhook.token}).`,
        }],
      };
    }
  • The MCP schema definition for the 'discord_create_webhook' tool.
    {
      name: "discord_create_webhook",
      description: "Create a webhook on a channel.",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          name: { type: "string", description: "Name for the webhook." },
          avatar: { type: "string", description: "Optional avatar URL for the webhook." },
        },
        required: ["channel_id", "name"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states the basic action. It doesn't mention whether this requires specific permissions, what happens on success/failure, rate limits, or what the webhook creation entails (e.g., returns a webhook URL). This leaves significant gaps for a mutation tool.

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?

The description is a single, efficient sentence that gets straight to the point with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what the tool returns (e.g., webhook object or URL), error conditions, or behavioral nuances. Given the complexity of creating a resource in Discord's API, more context is needed for effective use.

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 67% (2 of 3 parameters have descriptions), so the schema does moderate work. The description adds no parameter information beyond what's in the schema, but since coverage isn't low (<50%), the baseline 3 is appropriate. The description doesn't compensate for the undocumented 'channel_id' parameter.

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 clearly states the action ('Create') and resource ('webhook on a channel'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'discord_edit_webhook' or 'discord_delete_webhook', which would require more specific language about creation versus modification or removal.

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?

The description provides no guidance on when to use this tool versus alternatives like 'discord_edit_webhook' or 'discord_list_webhooks'. There's no mention of prerequisites (e.g., needing channel permissions) or typical use cases, leaving the agent to infer usage from context alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server