Skip to main content
Glama

discord_delete_webhook

Delete Discord webhooks by ID to manage integrations and remove unused endpoints. This tool removes webhooks from Discord servers to maintain clean configurations.

Instructions

Delete a webhook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
webhook_idYes

Implementation Reference

  • The handler logic for 'discord_delete_webhook' which fetches the webhook and deletes it.
    case "discord_delete_webhook": {
      const webhookId = validateId(args.webhook_id, "webhook_id");
      const webhook = await discord.fetchWebhook(webhookId);
      const webhookName = webhook.name;
      await webhook.delete();
      return { content: [{ type: "text", text: `✅ Webhook "${webhookName}" (id: ${webhookId}) deleted.` }] };
    }
  • Input schema definition for the 'discord_delete_webhook' tool.
      name: "discord_delete_webhook",
      description: "Delete a webhook.",
      inputSchema: {
        type: "object",
        properties: {
          webhook_id: { type: "string" },
        },
        required: ["webhook_id"],
      },
    },
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. 'Delete' implies a destructive operation, but the description doesn't mention whether this action is permanent, reversible, requires specific permissions, or has side effects. 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 extremely concise at just three words, front-loading the essential action and resource. There's zero wasted language, making it efficient for quick comprehension.

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 operation with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after deletion, whether there's confirmation, what permissions are required, or how to identify the webhook_id. This leaves too many unanswered questions for safe tool invocation.

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?

The description adds no parameter information beyond what's in the schema (which has 0% description coverage). However, with only one required parameter ('webhook_id'), the baseline is 4, but since the description provides zero parameter context, it's scored lower at 3 for failing to compensate for the schema's lack of descriptions.

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 ('Delete') and the resource ('a webhook'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'discord_delete_channel' or 'discord_delete_role' beyond the resource type, which prevents a perfect score.

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?

No guidance is provided about when to use this tool versus alternatives like 'discord_edit_webhook' or 'discord_list_webhooks'. The description offers no context about prerequisites, permissions needed, or typical scenarios for webhook deletion.

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