Skip to main content
Glama
luiso2

Evolution API WhatsApp MCP Server

by luiso2

create_group

Create WhatsApp groups for business communication by specifying participants, group name, and optional description using the Evolution API.

Instructions

Create a new WhatsApp group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoGroup description
instanceNameYesInstance name
participantsYesPhone numbers of participants
subjectYesGroup name

Implementation Reference

  • The main handler function for the 'create_group' MCP tool. It extracts arguments, calls the EvolutionAPI service to create the group, and returns the result as formatted text content.
    private async handleCreateGroup(args: any) {
      const result = await evolutionAPI.createGroup(args.instanceName, {
        subject: args.subject,
        participants: args.participants,
        description: args.description
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2)
          }
        ]
      };
    }
  • Input schema defining the parameters for the 'create_group' tool: instanceName, subject, participants (required), and optional description.
    inputSchema: {
      type: 'object',
      properties: {
        instanceName: { type: 'string', description: 'Instance name' },
        subject: { type: 'string', description: 'Group name' },
        participants: {
          type: 'array',
          items: { type: 'string' },
          description: 'Phone numbers of participants'
        },
        description: { type: 'string', description: 'Group description' }
      },
      required: ['instanceName', 'subject', 'participants']
    }
  • src/index.ts:337-353 (registration)
    Registration of the 'create_group' tool in the MCP tools array, used for listing available tools.
      name: 'create_group',
      description: 'Create a new WhatsApp group',
      inputSchema: {
        type: 'object',
        properties: {
          instanceName: { type: 'string', description: 'Instance name' },
          subject: { type: 'string', description: 'Group name' },
          participants: {
            type: 'array',
            items: { type: 'string' },
            description: 'Phone numbers of participants'
          },
          description: { type: 'string', description: 'Group description' }
        },
        required: ['instanceName', 'subject', 'participants']
      }
    },
  • Helper function in EvolutionAPI class that performs the actual HTTP POST request to the Evolution API endpoint /group/create/{instanceName} to create the group.
    async createGroup(instanceName: string, data: {
      subject: string;
      participants: string[];
      description?: string;
    }): Promise<Group> {
      const response = await this.client.post(`/group/create/${instanceName}`, data);
      return response.data;
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so the description carries the full burden. It only says 'Create a new WhatsApp group' without disclosing authentication requirements, side effects, or constraints like participant limits. Minimal behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, concise sentence that is front-loaded and to the point. It does not waste words, though it could be slightly expanded for context without losing conciseness.

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 4 parameters, no output schema, and no annotations, the description is incomplete. It does not explain what the return value is (e.g., group ID) or that an active instance is required. More context is needed.

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 coverage is 100% with descriptive parameter names and descriptions. The tool description does not add any extra meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 verb 'Create' and the resource 'a new WhatsApp group'. It distinguishes from sibling tools like 'add_participants' (modifies existing group) and 'list_groups' (lists groups).

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. It does not mention prerequisites (e.g., needing a connected instance) or any when-not scenarios. Implicit only from the name.

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