Skip to main content
Glama

delete_webhook

DestructiveIdempotent

Delete a webhook by providing its ID. Removes the specified webhook from your Eduframe account.

Instructions

Delete a webhook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the webhook to delete

Implementation Reference

  • Handler function for the delete_webhook tool. Takes an 'id' parameter, calls apiDelete on /webhooks/{id}, logs the response, and returns a formatted delete result.
      async ({ id }) => {
        try {
          const record = await apiDelete<EduframeRecord>(`/webhooks/${id}`);
          void logResponse("delete_webhook", { id }, record);
          return formatDelete(record, "webhook");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • Input schema for delete_webhook, requiring a positive integer 'id' parameter. Includes metadata: destructiveHint: true, idempotentHint: true.
    {
      description: "Delete a webhook.",
      annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
      inputSchema: { id: z.number().int().positive().describe("ID of the webhook to delete") },
    },
  • Registration of the delete_webhook tool via server.registerTool within registerWebhookTools function.
    server.registerTool(
      "delete_webhook",
      {
        description: "Delete a webhook.",
        annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
        inputSchema: { id: z.number().int().positive().describe("ID of the webhook to delete") },
      },
      async ({ id }) => {
        try {
          const record = await apiDelete<EduframeRecord>(`/webhooks/${id}`);
          void logResponse("delete_webhook", { id }, record);
          return formatDelete(record, "webhook");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • registerWebhookTools is listed in the tools array and invoked by registerAllTools to register all webhook tools including delete_webhook.
      registerWebhookTools,
    ];
    
    export function registerAllTools(server: McpServer): void {
      for (const register of tools) {
        register(server);
      }
  • The apiDelete helper function used by the handler to perform the actual HTTP DELETE request to the Eduframe API.
    /**
     * Perform a DELETE request to remove a resource.
     *
     * @param path - API path, e.g. "/leads/1"
     */
    export async function apiDelete<T>(path: string): Promise<T> {
      const { token } = getConfig();
      const url = buildUrl(path);
    
      const response = await fetch(url.toString(), {
        method: "DELETE",
        headers: buildHeaders(token),
      });
    
      return handleResponse<T>(response);
    }
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds no additional behavioral context beyond what annotations provide, so it meets the baseline but adds no extra value.

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, front-loaded sentence with no wasted words. Every part is necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete operation with one parameter and clear annotations, the description is complete. No additional context is needed.

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 coverage is 100% and the parameter 'id' is well-defined in the schema. The description does not add any extra semantics beyond the schema.

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 verb 'delete' and the resource 'webhook', making the action unambiguous. While it doesn't differentiate from other delete siblings, the tool name itself is specific enough.

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. There is no mention of prerequisites, side effects, or when not to use it.

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/martijnpieters/eduframe-mcp'

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