Skip to main content
Glama

Wapiworld WhatsApp API

by com.wapiworld
OverviewDiscussionsAdmin

Check webhook delivery health

list_webhook_subscriptions
Read-onlyIdempotent

Use this when someone asks whether their Wapiworld webhooks are working, failing or were switched off. Returns each subscription's endpoint scheme and host, events, active state, consecutive failures and an auto-disabled flag after 20 failures, 25 per page by default. Works only with an operator OAuth session, not an API key. Not for changing a webhook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoWebhook subscriptions per page, from 1 to 100; defaults to 25
cursorNoThe page.nextCursor of the previous page with the same projectId; absent for the first page
projectIdNoOnly this project

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesPass nextCursor as cursor, with the same filters, for the next page; null on the last page
webhookSubscriptionsYesDelivery health per subscription; autoDisabled marks an endpoint switched off after 20 consecutive failures. The signing secret, delivery paths, queries and fragments are never returned: hook paths often embed a credential.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque pagination cursor returned by a previous call"New value: +"The page.nextCursor of the previous page with the same projectId; absent for the first page"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum webhook subscriptions to return (default 25, maximum 100)"New value: +"Webhook subscriptions per page, from 1 to 100; defaults to 25"
    • changedInput schema / properties / projectId / description
      Previous value: -"Filter to one project id"New value: +"Only this project"
    • addedOutput schema / properties / page / description
      Added value: +"Pass nextCursor as cursor, with the same filters, for the next page; null on the last page"
    • addedOutput schema / properties / webhookSubscriptions / description
      Added value: +"Delivery health per subscription; autoDisabled marks an endpoint switched off after 20 consecutive failures. The signing secret, delivery paths, queries and fragments are never returned: hook paths often embed a credential."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds behavior beyond them: the 20-consecutive-failure auto-disable rule, the 25-per-page default, and the operator-OAuth-only auth requirement. These are concrete operational facts an agent could not derive from the 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?

Three front-loaded sentences: trigger, return shape, constraints. Efficient overall, though enumerating returned fields (endpoint, events, active state, failures) is partly redundant given an output schema exists.

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 read-only paginated list tool, the description covers trigger, auth mode, pagination, and the notable auto-disable behavior, and an output schema handles return values. An agent has everything needed to invoke it correctly.

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 the schema already documents limit, cursor and projectId thoroughly. The description only restates the page-size default and says nothing about cursor chaining or project scoping, so it adds no meaning beyond the schema; baseline 3 applies.

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 names a specific resource (webhook subscriptions) and its purpose (checking delivery health), and explicitly bounds it with 'Not for changing a webhook'. An agent can tell this apart from the instance/project/message siblings without opening a schema.

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?

It gives an explicit trigger ('when someone asks whether their webhooks are working, failing or were switched off'), a prerequisite ('only with an operator OAuth session, not an API key'), and an exclusion ('Not for changing a webhook'). Nothing about when to pick this tool is left to inference.

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

All Wapiworld WhatsApp API 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