Skip to main content
Glama

discord_edit_webhook

Modify Discord webhook properties including name, avatar, and channel assignment to update automated messaging configurations.

Instructions

Edit a webhook's name, avatar, or channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
webhook_idYes
nameNoNew name for the webhook.
avatarNoNew avatar URL for the webhook.
channel_idNoMove the webhook to a different channel.

Implementation Reference

  • The handler implementation for the `discord_edit_webhook` tool. It fetches the webhook using `discord.fetchWebhook` and then updates it using `webhook.edit` with the provided parameters (name, avatar, or channel_id).
    case "discord_edit_webhook": {
      const webhookId = validateId(args.webhook_id, "webhook_id");
      const webhook = await discord.fetchWebhook(webhookId);
      const editOptions: Record<string, unknown> = {};
      if (args.name !== undefined) editOptions.name = args.name as string;
      if (args.avatar !== undefined) editOptions.avatar = args.avatar as string;
      if (args.channel_id !== undefined) editOptions.channel = validateId(args.channel_id, "channel_id");
      await webhook.edit(editOptions);
      return { content: [{ type: "text", text: `✅ Webhook "${webhook.name}" (id: ${webhook.id}) updated.` }] };
    }
  • The definition and input schema for the `discord_edit_webhook` tool, specifying the required `webhook_id` and optional parameters.
    {
      name: "discord_edit_webhook",
      description: "Edit a webhook's name, avatar, or channel.",
      inputSchema: {
        type: "object",
        properties: {
          webhook_id: { type: "string" },
          name: { type: "string", description: "New name for the webhook." },
          avatar: { type: "string", description: "New avatar URL for the webhook." },
          channel_id: { type: "string", description: "Move the webhook to a different channel." },
        },
        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 the full burden of behavioral disclosure. It states the tool edits webhook attributes, implying a mutation, but doesn't cover critical aspects like required permissions, rate limits, whether changes are reversible, or what happens to unspecified fields. This leaves significant gaps in understanding the tool's behavior.

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 directly states the tool's function without unnecessary words. It is front-loaded and wastes no space, 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?

Given the tool's complexity as a mutation operation with no annotations and no output schema, the description is inadequate. It lacks details on behavioral traits, error handling, return values, and usage context, failing to compensate for the missing structured information.

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 75%, with three of four parameters having descriptions in the schema. The description adds minimal value by listing editable fields ('name, avatar, or channel'), which aligns with schema parameters but doesn't provide additional semantics beyond what's already documented. This meets the baseline for high schema coverage.

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 ('Edit') and resource ('a webhook's name, avatar, or channel'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'discord_create_webhook' or 'discord_delete_webhook', which would require mentioning it's for modifying existing webhooks versus creating or deleting them.

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, such as 'discord_create_webhook' for new webhooks or 'discord_delete_webhook' for removal. It also lacks prerequisites, like needing the webhook ID or appropriate permissions, 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/PaSympa/discord-mcp'

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