Skip to main content
Glama

server_create_webhook

Create webhooks for Minecraft servers to notify Discord or other services about events like server starts, stops, backups, and player activity.

Instructions

Create a new webhook for a Minecraft server. Supports Discord and other webhook types. Trigger events: server_start, server_stop, server_backup, player_join, player_leave, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID
webhook_typeYesWebhook type, e.g. 'Discord'
nameYesWebhook name
urlYesWebhook URL
bot_nameNoBot display name
triggerYesTrigger event: server_start, server_stop, server_backup, player_join, player_leave, etc.
bodyNoCustom webhook body template
enabledNoWhether webhook is active

Implementation Reference

  • The handler for 'server_create_webhook' which creates a new webhook for a Minecraft server using the provided client.
    server.tool(
      "server_create_webhook",
      "Create a new webhook for a Minecraft server. Supports Discord and other webhook types. Trigger events: server_start, server_stop, server_backup, player_join, player_leave, etc.",
      {
        server_id: z.string().describe("Server ID or UUID"),
        webhook_type: z.string().describe("Webhook type, e.g. 'Discord'"),
        name: z.string().describe("Webhook name"),
        url: z.string().url().describe("Webhook URL"),
        bot_name: z.string().optional().describe("Bot display name"),
        trigger: z
          .string()
          .describe(
            "Trigger event: server_start, server_stop, server_backup, player_join, player_leave, etc."
          ),
        body: z.string().optional().describe("Custom webhook body template"),
        enabled: z.boolean().default(true).describe("Whether webhook is active"),
      },
      async ({ server_id, ...webhookData }) => {
        try {
          const data = await client.post(
            `/servers/${server_id}/webhooks`,
            webhookData
          );
          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?

With no annotations provided, the description carries full burden but offers minimal behavioral disclosure. It mentions webhook types and trigger events but doesn't cover permissions needed, whether creation is idempotent, error conditions, rate limits, or what happens on success/failure. For a creation tool with 8 parameters, this leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two efficient sentences with zero waste. First sentence states core purpose, second provides useful examples. Well-structured and appropriately sized for the tool's complexity.

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 creation tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., returns webhook ID, confirmation message), error handling, or system behavior. The examples help but don't compensate for missing behavioral context needed for safe 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?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds marginal value by listing example webhook types ('Discord and other webhook types') and trigger events, but doesn't provide additional syntax, format, or constraint details beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Create a new webhook') and resource ('for a Minecraft server'), with specific examples of webhook types and trigger events. It distinguishes from siblings like server_delete_webhook and server_update_webhook by focusing on creation, but doesn't explicitly contrast with server_test_webhook or server_list_webhooks.

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 on when to use this tool versus alternatives like server_update_webhook or server_test_webhook. The description lists trigger events but doesn't specify prerequisites, constraints, or when-not-to-use scenarios. Usage context is implied but not explicit.

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