Skip to main content
Glama

WhatsApp

by io.github.mcp-dir

whatsapp_webhook_set

Set (or remove) this WhatsApp install's outbound webhook. Owner/admin only.

  • To set: pass url (https only, not localhost). events is the list of subscribed events ("permissions") — e.g. ["whatsapp.message"], or ["whatsapp.*"] for every WhatsApp event, or [] / omit for ALL events. See available_events from whatsapp_webhook_get. include_result (default true) controls whether the tool result is included in tool.call payloads. secret is optional (reserved).

  • Subscribing to any whatsapp.* event makes the daemon hold a live connection per number and forward inbound messages to your URL.

  • To remove the webhook: pass remove: true (or an empty url).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
eventsNo
removeNo
secretNo
include_resultNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations give no hints on permissions or side effects, but description explicitly states 'Owner/admin only' and explains that subscribing to whatsapp.* makes the daemon hold live connections, which is key behavioral context. It also notes https-only, no-localhost, and include_result default. This adds real value beyond annotations.

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?

Well-structured with bullet-like segments and clear separation of set vs remove modes. Slightly verbose in the events explanation, but every sentence carries necessary info. No fluff.

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?

Covers permissions (owner/admin), URL constraints, event semantics, side effects of live connection, and removal mode. Missing explicit return value description, but for a set operation the absence is acceptable. With no output schema, a note on what the tool returns would make it complete.

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

Parameters5/5

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

Schema coverage is 0% and params are just types. The description explains every parameter: url (https only, not localhost), events (examples, [] for all), include_result (default true), secret (optional/reserved), remove (boolean to remove). Also clarifies the relationship between url and remove. This is exemplary parameter documentation.

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 sets or removes an outbound webhook for a WhatsApp install, with owner/admin-only access. It explicitly distinguishes from the sibling tool whatsapp_webhook_get by focusing on the set/remove mutation side.

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

Usage Guidelines5/5

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

Provides explicit when-to-use instructions: passing `url` sets, `remove: true` (or empty url) removesched. It also mentions prerequisites (owner/admin only) and refers to whatsapp_webhook_get for available events. Clear contexts and mode distinction.

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

All WhatsApp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.8/5.0
Disambiguation3/5

There are many flattened action variants (e.g., whatsapp_chat_archive, whatsapp_chat_unarchive, whatsapp_chat_pin, etc.) that duplicate the same underlying action with similar descriptions, making it easy to select the wrong tool. However, some tools like whatsapp_send_text vs whatsapp_send_media are clearly distinct, and the group management tools share a common action pattern.

Naming Consistency4/5

Most tools follow a consistent `whatsapp_<resource>_<action>` pattern (e.g., whatsapp_chats, whatsapp_messages, whatsapp_group_members), with flattening creating multiple tools from the same action set. A few exceptions like `authenticate`, `connect`, `marketplace` break the pattern, but the WhatsApp-specific tools are largely consistent.

Tool Count2/5

47 tools is substantial, and many are flattened action variants (e.g., 6 chat state tools for archive/unarchive/pin/unpin/mute/unmute) that could be consolidated. The sheer number makes the tool list difficult to navigate, especially with non-WhatsApp tools like authenticate, marketplace, and report_bug mixed in. This feels over-scoped for a WhatsApp server.

Completeness4/5

The tool set covers core WhatsApp workflows: reading chats, contacts, groups, messages, sending messages/media, reacting, polls, search, history backfill, webhooks, and config. Minor gaps include lack of explicit voice message sending and perhaps advanced group settings, but most lifecycle operations are present.

Resources