Skip to main content
Glama

server_delete_webhook

Remove a webhook from a Minecraft server managed by crafty-mcp. Specify server and webhook IDs to delete unwanted notifications.

Instructions

Delete a webhook from a Minecraft server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
webhook_idYesWebhook ID to delete

Implementation Reference

  • The server_delete_webhook tool is registered and implemented within the registerServerWebhookTools function in src/tools/server-webhooks.ts. It takes server_id and webhook_id as inputs and performs a DELETE request to the server API.
    server.tool(
      "server_delete_webhook",
      "Delete a webhook from a Minecraft server",
      {
        server_id: z.string().describe("Server ID or UUID"),
        webhook_id: z.string().describe("Webhook ID to delete"),
      },
      async ({ server_id, webhook_id }) => {
        try {
          const data = await client.delete(
            `/servers/${server_id}/webhooks/${webhook_id}`
          );
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: `Error: ${msg}` }], isError: true };
        }
      }
    );
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. It states the tool deletes a webhook, implying a destructive mutation, but does not mention permissions required, whether the deletion is permanent, error handling, or any side effects. This is a significant gap 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 with the key information and has no redundant or verbose elements.

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 is a destructive mutation with no annotations and no output schema, the description is insufficient. It lacks details on behavioral aspects like permissions, consequences, or response format, making it incomplete for safe and effective use by an AI agent.

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 input schema has 100% description coverage, with clear documentation for both parameters ('server_id' and 'webhook_id'). The description adds no additional meaning beyond what the schema provides, such as format examples or relationships between parameters, so it meets the baseline score of 3 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 ('Delete') and the target ('a webhook from a Minecraft server'), which is specific and unambiguous. However, it does not explicitly differentiate from sibling tools like 'server_delete' or 'server_delete_task', which share the same verb but target different 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, such as 'server_update_webhook' for modifying webhooks or 'server_list_webhooks' for viewing them. It lacks context about prerequisites, like needing an existing webhook, or exclusions, such as not being usable for other server components.

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/HadiCherkaoui/crafty-mcp'

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