Skip to main content
Glama
jar285

MCP-Discord

by jar285

discord_delete_webhook

Delete Discord webhooks to remove automated message sources from channels, manage integrations, and maintain channel organization.

Instructions

Deletes an existing webhook for a Discord channel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
webhookIdYes
webhookTokenNo
reasonNo

Implementation Reference

  • Handler function for discord_delete_webhook tool. Parses arguments, fetches the webhook using Discord client, deletes it, and returns success or error response.
    case "discord_delete_webhook": {
      const { webhookId, webhookToken, reason } = DeleteWebhookSchema.parse(args);
      try {
        if (!client.isReady()) {
          return {
            content: [{ type: "text", text: "Discord client not logged in. Please use discord_login tool first." }],
            isError: true
          };
        }
    
        const webhook = await 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 {
          content: [{ type: "text", text: `Failed to delete webhook: ${error}` }],
          isError: true
        };
      }
    }
  • Zod schema for input validation of discord_delete_webhook tool parameters: webhookId (required), webhookToken (optional), reason (optional).
    const DeleteWebhookSchema = z.object({
        webhookId: z.string(),
        webhookToken: z.string().optional(),
        reason: z.string().optional()
    });
  • src/index.ts:445-457 (registration)
    Tool registration in the list of available tools, including name, description, and input schema definition.
    {
      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"]
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Deletes' implies a destructive mutation, the description lacks critical details such as permission requirements, whether the deletion is permanent or reversible, rate limits, or what happens upon success/failure. 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, direct sentence that efficiently conveys the core action without unnecessary words. It is front-loaded and appropriately sized for its purpose, with no wasted verbiage.

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?

Given the tool's complexity (a destructive operation with 3 parameters), lack of annotations, 0% schema description coverage, and no output schema, the description is insufficient. It does not address behavioral risks, parameter meanings, or expected outcomes, leaving significant gaps for an AI agent to understand and use the tool correctly.

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?

The input schema has 0% description coverage, and the tool description does not explain any parameters. It mentions 'webhook' but does not clarify what webhookId, webhookToken, or reason represent, their formats, or how they relate to the deletion process. With low schema coverage, the description fails to compensate for the lack of parameter documentation.

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 does not differentiate this tool from sibling tools like discord_delete_channel or discord_delete_message, which also perform deletion operations on different Discord resources.

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 does not mention prerequisites (e.g., needing a webhook ID), exclusions, or comparisons to sibling tools like discord_edit_webhook or discord_delete_channel, leaving the agent with no contextual usage information.

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

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