Skip to main content
Glama
billyfranklim1

mcp-evolution

Find Webhook

find_webhook

Fetch the current webhook URL and settings for your pinned WhatsApp instance to verify or troubleshoot message forwarding.

Instructions

Get the current webhook configuration for the pinned WhatsApp instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'registerFindWebhook' function registers the 'find_webhook' tool. The handler calls the Evolution API GET /webhook/find/{instanceName} and returns the webhook configuration as JSON.
    export function registerFindWebhook(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "find_webhook",
        {
          title: "Find Webhook",
          description: "Get the current webhook configuration for the pinned WhatsApp instance.",
          inputSchema: {},
        },
        async () => {
          try {
            const data = await client.get(`/webhook/find/${client.instanceName}`);
            return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
          } catch (e) {
            if (e instanceof McpError) return { isError: true, content: [{ type: "text" as const, text: e.message }] };
            throw e;
          }
        }
      );
    }
  • The tool is registered with the name 'find_webhook' via server.registerTool() in the registerFindWebhook function.
    export function registerFindWebhook(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "find_webhook",
        {
          title: "Find Webhook",
          description: "Get the current webhook configuration for the pinned WhatsApp instance.",
          inputSchema: {},
        },
        async () => {
          try {
            const data = await client.get(`/webhook/find/${client.instanceName}`);
            return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
          } catch (e) {
            if (e instanceof McpError) return { isError: true, content: [{ type: "text" as const, text: e.message }] };
            throw e;
          }
        }
      );
    }
  • The inputSchema is empty ({}), meaning this tool takes no input parameters.
      title: "Find Webhook",
      description: "Get the current webhook configuration for the pinned WhatsApp instance.",
      inputSchema: {},
    },
  • The 'registerFindWebhook' function is called in registerAllTools() to register the tool with the server.
    registerFindWebhook(server, client);
    registerSetWebhook(server, client);
Behavior3/5

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

Given no annotations, the description carries the burden. It implies a read-only, non-destructive operation for retrieving configuration. However, it does not disclose what happens if no webhook is set, authentication requirements, or response format, which would add transparency.

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?

Single sentence that is front-loaded and precise, with no extraneous information. Every word contributes to the 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?

For a simple retrieval tool with no parameters and no output schema, the description is largely complete. It states what is retrieved and from which instance. Could mention the return type or error cases, but current level is sufficient given simplicity.

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

Parameters4/5

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

Input schema has no parameters (100% coverage). The description adds meaning by specifying the scope ('pinned WhatsApp instance'), providing context beyond the schema. Baseline for zero-parameter tool is 4, and description meets it.

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 retrieves the current webhook configuration for the pinned WhatsApp instance, using a specific verb ('Get') and resource ('webhook configuration'). It effectively distinguishes from sibling tool 'set_webhook' which modifies the webhook.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description mentions 'for the pinned WhatsApp instance' but does not explain context, prerequisites, or when to prefer this over other webhook-related tools.

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/billyfranklim1/mcp-evolution'

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