Skip to main content
Glama
billyfranklim1

mcp-evolution

Leave Group

leave_group

Leave a WhatsApp group by providing the group JID. Removes the pinned instance from the specified group.

Instructions

Leave a WhatsApp group via the pinned instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupJidYesGroup JID to leave (e.g. 120363000000000000@g.us)

Implementation Reference

  • The registerLeaveGroup function registers the 'leave_group' tool with the MCP server. The handler sends a DELETE request to /group/leaveGroup/{instanceName}?groupJid={encodedJid} via the EvolutionClient, returning the response as text content.
    export function registerLeaveGroup(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "leave_group",
        {
          title: "Leave Group",
          description: "Leave a WhatsApp group via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const data = await client.delete(
              `/group/leaveGroup/${client.instanceName}?groupJid=${encodeURIComponent(args.groupJid)}`
            );
            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;
          }
        }
      );
    }
  • Input schema for 'leave_group': requires a single 'groupJid' parameter (string) describing the WhatsApp group JID to leave.
    const schema = {
      groupJid: z.string().min(1).describe("Group JID to leave (e.g. 120363000000000000@g.us)"),
    };
  • Import of registerLeaveGroup from the leave-group module into the central tools index.
    import { registerLeaveGroup } from "./leave-group.js";
  • Registration call: registerLeaveGroup(server, client) within registerAllTools, called from src/server.ts line 16.
    registerLeaveGroup(server, client);
  • EvolutionClient.delete method is the HTTP helper used by the leave_group handler to send the DELETE request to the Evolution API.
    async delete<T = unknown>(path: string, body?: unknown): Promise<T> {
      return this.request<T>("DELETE", path, body);
    }
    
    private async request<T>(method: string, path: string, body?: unknown): Promise<T> {
      const url = `${this.baseUrl}${path}`;
      const headers: Record<string, string> = {
        apikey: this.apiKey,
        "Content-Type": "application/json",
      };
    
      const res = await fetch(url, {
        method,
        headers,
        body: body !== undefined ? JSON.stringify(body) : undefined,
      });
    
      const text = await res.text();
    
      if (!res.ok) {
        throw new McpError(
          ErrorCode.InternalError,
          `Evolution API error ${res.status}: ${text}`
        );
      }
    
      try {
        return JSON.parse(text) as T;
      } catch {
        return text as unknown as T;
      }
    }
Behavior2/5

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

No annotations provided, so description should disclose behavioral traits. Only mentions 'via pinned instance' but no side effects (e.g., irreversible, requires being participant). Lacks detail for a mutation tool.

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, front-loaded, no unnecessary words. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 1-param tool with no output schema, description is adequate but missing behavioral context like irreversibility or participant requirements. Could be improved.

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 baseline is 3. Description doesn't add meaning beyond the schema (e.g., format or constraints).

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 action (leave) and resource (WhatsApp group), and specifies it's via the pinned instance. It distinguishes from siblings like 'create_group' or 'update_group_subject'.

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 guidance on when to use this tool versus alternatives (e.g., 'remove participant' for removing others). No exclusions or prerequisites mentioned.

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