Skip to main content
Glama
luiso2

Evolution API WhatsApp MCP Server

by luiso2

remove_participants

Remove specified participants from a WhatsApp group using their phone numbers to manage group membership and maintain appropriate conversation environments.

Instructions

Remove participants from a group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupJidYesGroup JID
instanceNameYesInstance name
participantsYesPhone numbers to remove

Implementation Reference

  • The MCP tool handler function that executes the remove_participants logic by calling the EvolutionAPI service.
    private async handleRemoveParticipants(args: any) {
      const result = await evolutionAPI.removeGroupParticipants(args.instanceName, {
        groupJid: args.groupJid,
        participants: args.participants
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2)
          }
        ]
      };
    }
  • Input schema definition for the remove_participants tool.
    {
      name: 'remove_participants',
      description: 'Remove participants from a group',
      inputSchema: {
        type: 'object',
        properties: {
          instanceName: { type: 'string', description: 'Instance name' },
          groupJid: { type: 'string', description: 'Group JID' },
          participants: {
            type: 'array',
            items: { type: 'string' },
            description: 'Phone numbers to remove'
          }
        },
        required: ['instanceName', 'groupJid', 'participants']
      }
  • src/index.ts:536-537 (registration)
    Registration of the tool handler in the MCP call tool request switch statement.
    case 'remove_participants':
      return await this.handleRemoveParticipants(args);
  • Helper method in EvolutionAPI service that makes the HTTP POST request to remove group participants.
    async removeGroupParticipants(instanceName: string, data: {
      groupJid: string;
      participants: string[];
    }): Promise<any> {
      const response = await this.client.post(`/group/removeParticipants/${instanceName}`, data);
      return response.data;
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as required permissions, whether removal is reversible, error conditions (e.g., invalid participants), or side effects (e.g., notifications to group).

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, clear sentence with zero waste. It's appropriately sized and front-loaded, efficiently conveying the core purpose without unnecessary elaboration.

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

Completeness2/5

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

Given no annotations, no output schema, and a mutation tool with potential side effects, the description is incomplete. It lacks details on behavior, outcomes, or error handling, leaving significant gaps for an agent to use 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 parameters are documented in the schema. The description adds no additional meaning beyond implying 'group' and 'participants' as targets, which the schema already covers with 'groupJid' and 'participants'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Remove') and resource ('participants from a group'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'add_participants' beyond the verb difference, missing explicit comparison.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing group), exclusions, or how it relates to sibling tools like 'add_participants' or 'create_group'.

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

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