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;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a write operation ('add') but doesn't disclose permissions needed, rate limits, error conditions, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence with zero waste. It's front-loaded and appropriately sized for the tool's complexity, making it easy to parse quickly.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks crucial context like required permissions, what the response contains, error handling, or how it interacts with sibling tools (e.g., 'remove_participants').

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 'participants' are added to a 'group', which is already clear from the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('add') and resource ('participants to a group'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'remove_participants' or 'create_group', which would require mentioning it's for existing groups only.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., group must exist), exclusions (e.g., cannot add participants to non-existent groups), or related tools like 'remove_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