Skip to main content
Glama

discord_delete_webhook

Delete an existing Discord webhook to remove automated message delivery from a channel. This tool removes webhooks by ID and token, with optional audit log reason.

Instructions

Deletes an existing webhook for a Discord channel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
webhookIdYes
webhookTokenNo
reasonNo

Implementation Reference

  • The core handler function that implements the discord_delete_webhook tool logic: validates input, fetches the webhook, deletes it, and handles errors.
    export async function deleteWebhookHandler(
      args: unknown,
      context: ToolContext
    ): Promise<ToolResponse> {
      const { webhookId, webhookToken, reason } = DeleteWebhookSchema.parse(args);
      try {
        if (!context.client.isReady()) {
          return {
            content: [{ type: 'text', text: 'Discord client not logged in.' }],
            isError: true,
          };
        }
    
        const webhook = await context.client.fetchWebhook(webhookId, webhookToken);
        if (!webhook) {
          return {
            content: [
              { type: 'text', text: `Cannot find webhook with ID: ${webhookId}` },
            ],
            isError: true,
          };
        }
    
        // Delete the webhook
        await webhook.delete(reason || 'Webhook deleted via API');
    
        return {
          content: [
            {
              type: 'text',
              text: `Successfully deleted webhook with ID: ${webhook.id}`,
            },
          ],
        };
      } catch (error) {
        return handleDiscordError(error);
      }
    }
  • Tool metadata and input schema definition used for MCP tools/list response.
    {
      name: 'discord_delete_webhook',
      description: 'Deletes an existing webhook for a Discord channel',
      inputSchema: {
        type: 'object',
        properties: {
          webhookId: { type: 'string' },
          webhookToken: { type: 'string' },
          reason: { type: 'string' },
        },
        required: ['webhookId'],
      },
    },
  • Zod validation schema parsed in the handler for input parameters.
    export const DeleteWebhookSchema = z.object({
      webhookId: z.string(),
      webhookToken: z.string().optional(),
      reason: z.string().optional(),
    });
  • src/server.ts:204-207 (registration)
    Dispatch registration in the main MCP server CallToolRequestSchema handler switch statement.
    case 'discord_delete_webhook':
      this.logClientState('before discord_delete_webhook handler');
      toolResponse = await deleteWebhookHandler(args, this.toolContext);
      return toolResponse;
  • Dispatch case in the HTTP transport handler for direct method calls.
    case 'discord_delete_webhook':
      result = await deleteWebhookHandler(params, this.toolContext!);
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. It states the tool deletes a webhook, implying a destructive mutation, but lacks details on permissions required, whether deletion is permanent/reversible, rate limits, or response behavior. This is inadequate for a mutation tool with zero annotation coverage.

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 with zero wasted words. It's front-loaded with the core action and resource, making it easy to scan and understand 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 destructive mutation tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks parameter explanations, behavioral details, and usage context, making it insufficient for safe and effective tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions no parameters at all, failing to explain webhookId, webhookToken, or reason. This leaves three parameters with no semantic context beyond the schema's basic types.

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 ('Deletes') and resource ('an existing webhook for a Discord channel'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like discord_delete_channel or discord_delete_message, which target different resources, so it misses full sibling distinction.

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. It doesn't mention prerequisites (e.g., needing webhook ID/token), exclusions, or compare to related tools like discord_edit_webhook or discord_delete_channel, leaving usage context unclear.

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/IQAIcom/mcp-discord'

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