Skip to main content
Glama

whatsmcp

by com.whatsmcp
OverviewDiscussionsAdmin

Pause or Resume Webhook

wa_enable_webhook
Idempotent

Pause or resume delivery to the configured webhook WITHOUT changing the endpoint or its signing secret. Use this to stop deliveries temporarily — deleting and re-creating the webhook would issue a new secret. Messages keep arriving while paused and stay readable with wa_list_messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNooptional note recorded with a pause, shown in the console
enabledYestrue resumes delivery, false pauses it; the endpoint and its signing secret are kept either way

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
enabledYes
refusalNopresent only when the request was declined

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / refusal / properties / account_status
      Added value: +{
+  "description": "when the number is not working: its status — starting, not_running, whatsapp_down, suspended, pairing, unlinked or locked",
+  "type": "string"
+}
    • addedOutput schema / properties / refusal / properties / account_status_reason
      Added value: +{
+  "description": "the detail of account_status, e.g. no_egress, stopped, no_plan",
+  "type": "string"
+}
    • addedOutput schema / properties / refusal / properties / since
      Added value: +{
+  "description": "when the number stopped working, RFC3339, when known",
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare non-destructive and idempotent, and the description builds on that with the concrete reason: the endpoint and signing secret survive the toggle, so there is no re-pairing cost. It also discloses the side effect that messages keep arriving while paused and remain readable via wa_list_messages, which is genuinely non-obvious behavior an agent could not infer.

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?

Three tight sentences: what it does, why not to use the destructive alternative, and what happens to in-flight messages. No redundancy and the core guarantee is front-loaded.

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?

With an output schema present, return values need not be described; annotations cover safety and idempotency; both parameters are fully documented in the schema. The description closes the remaining gap — reversibility and message handling during pause — leaving nothing material unstated for a two-parameter toggle.

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 both `enabled` and `reason` are already documented in the schema. The description restates only the preservation guarantee for `enabled` and adds nothing about the console-visible `reason` note, so it does not exceed the baseline.

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?

States a specific action pair (pause/resume delivery) on a specific resource (the configured webhook), and immediately clarifies scope: the endpoint and signing secret are untouched. It differentiates from siblings wa_delete_webhook and wa_set_webhook by naming the delete/re-create path as the wrong alternative.

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?

Explicitly says when to use it ('to stop deliveries temporarily') and when not to (deleting and re-creating, because that issues a new secret). The `enabled` boolean semantics are reinforced as the mechanism for choosing pause vs resume.

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

All whatsmcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources