Skip to main content
Glama
webflow

Webflow

Official
by webflow

Data Webhook Tool

data_webhook_tool

Manage Webflow site webhooks: list, create, get details, or delete webhook registrations for specific trigger events.

Instructions

Data tool - Webhook tool to perform actions like list webhooks, create webhooks, get webhook details, and delete webhooks for a Webflow site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionsYes

Implementation Reference

  • The tool 'data_webhook_tool' is registered via server.registerTool() with inputSchema defining actions (list_webhooks, create_webhook, get_webhook, delete_webhook).
    server.registerTool(
      "data_webhook_tool",
      {
        title: "Data Webhook Tool",
        annotations: {
          readOnlyHint: false,
          openWorldHint: true,
        },
        description:
          "Data tool - Webhook tool to perform actions like list webhooks, create webhooks, get webhook details, and delete webhooks for a Webflow site.",
        inputSchema: {
          actions: z.array(
            z
              .object({
                // GET https://api.webflow.com/v2/sites/:site_id/webhooks
                list_webhooks: z
                  .object({
                    site_id: z
                      .string()
                      .describe(
                        "The site's unique ID, used to list its registered webhooks."
                      ),
                  })
                  .optional()
                  .describe(
                    "List all App-created webhooks registered for a given site. Returns webhook details including trigger type, URL, and creation date."
                  ),
                // POST https://api.webflow.com/v2/sites/:site_id/webhooks
                create_webhook: z
                  .object({
                    site_id: z
                      .string()
                      .describe(
                        "The site's unique ID, used to create a webhook for this site."
                      ),
                    trigger_type: z
                      .enum([
                        "form_submission",
                        "site_publish",
                        "page_created",
                        "page_metadata_updated",
                        "page_deleted",
                        "ecomm_new_order",
                        "ecomm_order_changed",
                        "ecomm_inventory_changed",
                        "user_account_added",
                        "user_account_updated",
                        "user_account_deleted",
                        "collection_item_created",
                        "collection_item_changed",
                        "collection_item_deleted",
                        "collection_item_published",
                        "collection_item_unpublished",
                        "comment_created",
                      ])
                      .describe(
                        "The type of event that triggers the webhook. Choose from 17 supported trigger types."
                      ),
                    url: z
                      .string()
                      .url()
                      .describe(
                        "The URL that will receive the webhook POST request when the event is triggered."
                      ),
                    filter: z
                      .object({
                        name: z
                          .string()
                          .optional()
                          .describe(
                            "The name of the form to receive notifications for."
                          ),
                      })
                      .optional()
                      .describe(
                        "Only supported for the 'form_submission' trigger type. Filter for a specific form by name."
                      ),
                  })
                  .optional()
                  .describe(
                    "Create a new webhook for a site. Limit of 75 registrations per trigger type, per site."
                  ),
                // GET https://api.webflow.com/v2/webhooks/:webhook_id
                get_webhook: z
                  .object({
                    webhook_id: z
                      .string()
                      .describe(
                        "The webhook's unique ID, used to retrieve its details."
                      ),
                  })
                  .optional()
                  .describe(
                    "Get detailed information about a specific webhook including its trigger type, URL, and last triggered date."
                  ),
                // DELETE https://api.webflow.com/v2/webhooks/:webhook_id
                delete_webhook: z
                  .object({
                    webhook_id: z
                      .string()
                      .describe(
                        "The webhook's unique ID, used to identify which webhook to remove."
                      ),
                  })
                  .optional()
                  .describe("Remove a webhook registration."),
              })
              .strict()
              .refine(
                (d) =>
                  [
                    d.list_webhooks,
                    d.create_webhook,
                    d.get_webhook,
                    d.delete_webhook,
                  ].filter(Boolean).length >= 1,
                {
                  message:
                    "Provide at least one of list_webhooks, create_webhook, get_webhook, delete_webhook.",
                }
              )
          ),
        },
      },
      async ({ actions }) => {
        const result: Content[] = [];
        try {
          for (const action of actions) {
            if (action.list_webhooks) {
              const content = await listWebhooks(action.list_webhooks);
              result.push(textContent(content));
            }
            if (action.create_webhook) {
              const content = await createWebhook(action.create_webhook);
              result.push(textContent(content));
            }
            if (action.get_webhook) {
              const content = await getWebhook(action.get_webhook);
              result.push(textContent(content));
            }
            if (action.delete_webhook) {
              const content = await deleteWebhook(action.delete_webhook);
              result.push(textContent(content));
            }
          }
          return toolResponse(result);
        } catch (error) {
          return formatErrorResponse(error);
        }
      }
    );
  • The handler callback for data_webhook_tool that processes each action (list, create, get, delete webhooks) by calling the appropriate helper functions.
    async ({ actions }) => {
      const result: Content[] = [];
      try {
        for (const action of actions) {
          if (action.list_webhooks) {
            const content = await listWebhooks(action.list_webhooks);
            result.push(textContent(content));
          }
          if (action.create_webhook) {
            const content = await createWebhook(action.create_webhook);
            result.push(textContent(content));
          }
          if (action.get_webhook) {
            const content = await getWebhook(action.get_webhook);
            result.push(textContent(content));
          }
          if (action.delete_webhook) {
            const content = await deleteWebhook(action.delete_webhook);
            result.push(textContent(content));
          }
        }
        return toolResponse(result);
      } catch (error) {
        return formatErrorResponse(error);
      }
    }
  • Helper function 'listWebhooks' that calls WebflowClient.webhooks.list().
    const listWebhooks = async (arg: { site_id: string }) => {
      const response = await getClient().webhooks.list(
        arg.site_id,
        requestOptions
      );
      return response;
    };
  • Helper function 'createWebhook' that calls WebflowClient.webhooks.create().
    const createWebhook = async (arg: {
      site_id: string;
      trigger_type: string;
      url: string;
      filter?: { name?: string };
    }) => {
      const response = await getClient().webhooks.create(
        arg.site_id,
        {
          triggerType: arg.trigger_type as any,
          url: arg.url,
          filter: arg.filter,
        },
        requestOptions
      );
      return response;
    };
  • Helper function 'getWebhook' that calls WebflowClient.webhooks.get().
    const getWebhook = async (arg: { webhook_id: string }) => {
      const response = await getClient().webhooks.get(
        arg.webhook_id,
        requestOptions
      );
      return response;
    };
  • Helper function 'deleteWebhook' that calls WebflowClient.webhooks.delete().
    const deleteWebhook = async (arg: { webhook_id: string }) => {
      const response = await getClient().webhooks.delete(
        arg.webhook_id,
        requestOptions
      );
      return response;
    };
Behavior3/5

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

Annotations indicate readOnlyHint=false and openWorldHint=true, which the description aligns with by mentioning mutations (create, delete). However, the description adds no additional behavioral context, such as side effects, rate limits, or irreversibility, beyond what annotations already imply.

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

Conciseness3/5

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

The description is very concise (one sentence, 20 words) but lacks necessary detail. It front-loads the purpose but is under-informative, sacrificing completeness for brevity.

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 (multiple actions, nested schema), the description is overly sparse. It does not explain the action selection mechanism, site_id requirement, or trigger types, forcing the agent to rely solely on the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool description (0% schema coverage) does not explain the 'actions' parameter or its nested structure. While the input schema contains detailed descriptions, the description itself adds no semantic value to the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: performing webhook actions (list, create, get, delete) for a Webflow site. It uses a specific verb ('perform') and identifies the resource ('webhooks for a Webflow site'), distinguishing it from sibling data tools.

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, nor does it mention prerequisites or exclusions. It merely lists actions without contextualizing usage.

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/webflow/mcp-server'

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