Skip to main content
Glama
ExoCubeYT

OpenWA MCP Server

by ExoCubeYT

list_webhooks

Retrieve all webhooks for a WhatsApp session to view and manage event notifications.

Instructions

List all webhooks configured for a WhatsApp session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID

Implementation Reference

  • The tool 'list_webhooks' is registered via server.registerTool along with its schema definition.
    export function registerWebhookTools(server: McpServer) {
      server.registerTool(
        "list_webhooks",
        {
          description: "List all webhooks configured for a WhatsApp session",
          inputSchema: {
            sessionId: z.string().describe("Session ID"),
          },
        },
        async ({ sessionId }) => {
          const data = await openwaClient({ method: "GET", path: `/sessions/${sessionId}/webhooks` });
          return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
        }
      );
  • The handler function for 'list_webhooks' that makes a GET request to /sessions/{sessionId}/webhooks and returns the result.
    server.registerTool(
      "list_webhooks",
      {
        description: "List all webhooks configured for a WhatsApp session",
        inputSchema: {
          sessionId: z.string().describe("Session ID"),
        },
      },
      async ({ sessionId }) => {
        const data = await openwaClient({ method: "GET", path: `/sessions/${sessionId}/webhooks` });
        return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
      }
  • Input schema for list_webhooks: requires sessionId (string).
    {
      description: "List all webhooks configured for a WhatsApp session",
      inputSchema: {
        sessionId: z.string().describe("Session ID"),
      },
    },
  • The openwaClient helper that performs the actual HTTP request to the OpenWA API.
    export async function openwaClient<T = unknown>(opts: RequestOptions): Promise<T> {
      const url = `${BASE_URL}${opts.path}`;
    
      const headers: Record<string, string> = {
        "Content-Type": "application/json",
        "X-API-Key": API_KEY,
      };
    
      const res = await fetch(url, {
        method: opts.method,
        headers,
        body: opts.body ? JSON.stringify(opts.body) : undefined,
      });
    
      const text = await res.text();
    
      if (!res.ok) {
        throw new Error(`OpenWA API ${res.status}: ${text}`);
      }
    
      try {
        return JSON.parse(text) as T;
      } catch {
        return text as T;
      }
    }
  • src/index.ts:9-9 (registration)
    Import of registerWebhookTools from webhooks.ts.
    import { registerWebhookTools } from "./tools/webhooks.js";
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'List' (a read operation) but omits details like whether authentication is required, rate limits, or behavior if the session is invalid. This is insufficient for a tool with no annotations.

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?

The description is a single, concise sentence with no filler. Every word is necessary and directly communicates the tool's purpose.

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?

Given the tool's simplicity (1 parameter, no output schema), the description is mostly complete. It could optionally mention the return format (list of webhook objects) or pagination, but the current version is adequate for basic comprehension.

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?

The input schema has 100% coverage (sessionId described as 'Session ID'). The description adds no additional meaning beyond the schema, meeting the baseline for high schema coverage.

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 'List all webhooks configured for a WhatsApp session' uses a specific verb ('List') and resource ('webhooks') with a clear scope ('for a WhatsApp session'). It distinguishes itself from sibling tools like create_webhook, delete_webhook, and update_webhook by focusing on listing.

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?

The description does not provide explicit when-to-use or when-not-to-use guidance. It is implied that this tool is for retrieving all webhooks, but no alternatives or exclusions are mentioned despite the presence of sibling tools like get_webhook or search_webhook.

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/ExoCubeYT/openwa-mcp'

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