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;
    }
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 only states the basic action without behavioral details. It doesn't disclose permissions needed, whether creation is reversible, rate limits, 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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, 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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or dependencies (e.g., instance must be connected). Given the complexity and lack of structured data, more context is needed for effective use.

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 well-documented in the schema itself. The description adds no additional parameter semantics beyond implying a WhatsApp context, which the schema already covers with parameter descriptions like 'Group description'. Baseline 3 is appropriate as 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 action ('Create') and resource ('new WhatsApp group'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_groups' or specify what distinguishes this creation from other group-related operations, keeping it from a perfect score.

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. For example, it doesn't mention prerequisites like needing an active instance (implied by 'instanceName' parameter) or how it relates to sibling tools like 'add_participants' for modifying existing groups, leaving usage context unclear.

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