Skip to main content
Glama
wuapidev

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create a webhook endpoint

create_webhook

Register a public HTTPS URL to receive selected events as signed POST requests, then reveal the signing secret in the wuapi dashboard.

Instructions

Register a public https URL to receive events as signed POST requests. The signing secret is not returned through this tool, to keep it out of the conversation: the user reveals it in the wuapi dashboard (Webhooks, rotate the endpoint's secret) and stores it with their server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic https URL that answers 2xx within 10 seconds.
eventsYesEvent types to receive, such as `message.received`, `message.sent`, `message.failed`, `account.connected`, `account.disconnected`.
projectIdNoOrganization keys only: the project to create it in (id or `ext:<externalId>`). A project key always uses its own project.
idempotencyKeyNoOptional. Reuse the same key when retrying this exact call: within 24 hours wuapi returns the first result instead of doing it twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.0
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "account.qr_code_issued",
-  "account.pairing_code_issued",
-  "account.connected",
-  "account.disconnected",
-  "account.failed",
-  "message.received",
-  "message.sent",
-  "message.delivered",
-  "message.read",
-  "message.failed",
-  "message.edited",
-  "message.deleted",
-  "message.media_downloaded",
-  "poll.voted",
-  "group.joined",
-  "group.updated",
-  "group.join_requested",
-  "group.join_request_revoked",
-  "chat.updated",
-  "chat.presence_updated",
-  "contact.presence_updated",
-  "contact.picture_updated",
-  "contact.updated",
-  "blocklist.updated",
-  "label.updated",
-  "call.received",
-  "call.ended",
-  "channel.message_received",
-  "channel.message_updated",
-  "channel.updated",
-  "history.synced",
-  "project.created",
-  "project.updated",
-  "project.deleted",
-  "invitation.status_changed"
-]New value: +[
+  "account.qr_code_issued",
+  "account.pairing_code_issued",
+  "account.connected",
+  "account.disconnected",
+  "account.failed",
+  "message.received",
+  "message.sent",
+  "message.delivered",
+  "message.read",
+  "message.failed",
+  "message.edited",
+  "message.deleted",
+  "message.media_downloaded",
+  "story.received",
+  "story.deleted",
+  "story.viewed",
+  "story.reacted",
+  "poll.voted",
+  "group.joined",
+  "group.updated",
+  "group.join_requested",
+  "group.join_request_revoked",
+  "chat.updated",
+  "chat.presence_updated",
+  "contact.presence_updated",
+  "contact.picture_updated",
+  "contact.updated",
+  "blocklist.updated",
+  "sticker.favorites_updated",
+  "label.updated",
+  "call.received",
+  "call.ended",
+  "channel.message_received",
+  "channel.message_updated",
+  "channel.updated",
+  "history.synced",
+  "project.created",
+  "project.updated",
+  "project.deleted",
+  "invitation.status_changed"
+]
  2. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "account.qr_code_issued",
-  "account.pairing_code_issued",
-  "account.connected",
-  "account.disconnected",
-  "account.failed",
-  "message.received",
-  "message.sent",
-  "message.delivered",
-  "message.read",
-  "message.failed",
-  "message.edited",
-  "message.deleted",
-  "poll.voted",
-  "group.joined",
-  "group.updated",
-  "group.join_requested",
-  "group.join_request_revoked",
-  "chat.updated",
-  "chat.presence_updated",
-  "contact.presence_updated",
-  "contact.picture_updated",
-  "contact.updated",
-  "blocklist.updated",
-  "label.updated",
-  "call.received",
-  "call.ended",
-  "channel.message_received",
-  "channel.message_updated",
-  "channel.updated",
-  "history.synced",
-  "project.created",
-  "project.updated",
-  "project.deleted",
-  "invitation.status_changed"
-]New value: +[
+  "account.qr_code_issued",
+  "account.pairing_code_issued",
+  "account.connected",
+  "account.disconnected",
+  "account.failed",
+  "message.received",
+  "message.sent",
+  "message.delivered",
+  "message.read",
+  "message.failed",
+  "message.edited",
+  "message.deleted",
+  "message.media_downloaded",
+  "poll.voted",
+  "group.joined",
+  "group.updated",
+  "group.join_requested",
+  "group.join_request_revoked",
+  "chat.updated",
+  "chat.presence_updated",
+  "contact.presence_updated",
+  "contact.picture_updated",
+  "contact.updated",
+  "blocklist.updated",
+  "label.updated",
+  "call.received",
+  "call.ended",
+  "channel.message_received",
+  "channel.message_updated",
+  "channel.updated",
+  "history.synced",
+  "project.created",
+  "project.updated",
+  "project.deleted",
+  "invitation.status_changed"
+]
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the mutation safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower, and the description clears it by disclosing a non-obvious behavior: the signing secret is deliberately withheld from the tool response and must be retrieved out-of-band from the dashboard. That is exactly the kind of consequence an agent must relay to a user. It does not cover retry/delivery semantics or what the call returns, keeping it from a 5.

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 sentences, front-loaded with the core action, and the second sentence carries the critical secret-handling caveat rather than filler. The parenthetical with the dashboard path is slightly dense but each clause is actionable, so no material waste.

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

Completeness4/5

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

With no output schema, the description compensates on the single most dangerous gap — that the secret is not returned — and the schema carries the parameter contract. It omits what the successful response looks like (endpoint id, etc.), which an agent would need to chain into update_webhook or delete_webhook, so it is strong but not fully complete.

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 all four parameters (url, events, projectId, idempotencyKey) are already fully documented in the schema, including the https pattern, the 2xx/10s contract, and the idempotency behavior. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 states a specific verb and resource: "Register a public https URL to receive events as signed POST requests." That is unambiguous about what the tool does and what it produces. It does not, however, name or distinguish itself from the sibling mutators update_webhook/delete_webhook/list_webhooks, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied — you call this to create a new endpoint — but there is no explicit guidance on when to use create_webhook versus update_webhook for an existing endpoint, nor any precondition stated (e.g. one endpoint per event set). It adds a practical workflow note about the signing secret, which is useful context but not routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools