Skip to main content
Glama
luiso2

Evolution API WhatsApp MCP Server

by luiso2

add_participants

Add phone numbers to a WhatsApp group using Evolution API to expand group membership for business messaging and communication.

Instructions

Add participants to a group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupJidYesGroup JID
instanceNameYesInstance name
participantsYesPhone numbers to add

Implementation Reference

  • MCP tool handler for 'add_participants' that delegates to EvolutionAPI and formats the response.
    private async handleAddParticipants(args: any) {
      const result = await evolutionAPI.addGroupParticipants(args.instanceName, {
        groupJid: args.groupJid,
        participants: args.participants
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2)
          }
        ]
      };
  • Input schema defining parameters for the add_participants tool.
    {
      name: 'add_participants',
      description: 'Add participants to 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 add'
          }
        },
        required: ['instanceName', 'groupJid', 'participants']
      }
    },
  • src/index.ts:534-535 (registration)
    Registration of the tool handler in the switch case for CallToolRequest.
    case 'add_participants':
      return await this.handleAddParticipants(args);
  • Helper method in EvolutionAPI that performs the HTTP POST to add participants to a group via the Evolution API backend.
    async addGroupParticipants(instanceName: string, data: {
      groupJid: string;
      participants: string[];
    }): Promise<any> {
      const response = await this.client.post(`/group/addParticipants/${instanceName}`, data);
      return response.data;
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the action without disclosing behavioral traits like authentication needs, rate limits, or what happens if participants already exist or are invalid.

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 with no waste. Perfectly concise for the information provided.

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 the tool mutates state, has 3 required parameters, and no output schema or annotations, the description should provide more context (e.g., return value, side effects). It is too minimal.

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. The description does not add extra meaning beyond the parameter names and types (e.g., format of phone numbers or groupJid).

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 ('Add participants') and the resource ('to a group'). It distinguishes from siblings like 'remove_participants' and 'create_group', though it could be more explicit about the scope.

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 vs alternatives. Sibling 'remove_participants' exists but is not mentioned. No prerequisites or context provided.

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