Skip to main content
Glama
billyfranklim1

mcp-evolution

Create Group

create_group

Create a new WhatsApp group by specifying a subject and participant phone numbers. Optionally add a group description.

Instructions

Create a new WhatsApp group via the pinned instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesGroup name/subject
descriptionNoOptional group description
participantsYesArray of participant phone numbers or JIDs

Implementation Reference

  • Input schema for create_group: subject (string), description (optional string), participants (array of strings, min 1).
    const schema = {
      subject: z.string().min(1).describe("Group name/subject"),
      description: z.string().optional().describe("Optional group description"),
      participants: z.array(z.string().min(1)).min(1).describe("Array of participant phone numbers or JIDs"),
    };
  • Handler function registerCreateGroup: registers the 'create_group' tool on the MCP server. It POSTs to /group/create/{instanceName} with subject, participants, and optionally description, then returns the JSON response.
    export function registerCreateGroup(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "create_group",
        {
          title: "Create Group",
          description: "Create a new WhatsApp group via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const payload: Record<string, unknown> = {
              subject: args.subject,
              participants: args.participants,
            };
            if (args.description) payload["description"] = args.description;
            const data = await client.post(`/group/create/${client.instanceName}`, payload);
            return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
          } catch (e) {
            if (e instanceof McpError) return { isError: true, content: [{ type: "text" as const, text: e.message }] };
            throw e;
          }
        }
      );
    }
  • Registration: server.registerTool('create_group', ...) with input schema and handler.
    export function registerCreateGroup(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "create_group",
        {
          title: "Create Group",
          description: "Create a new WhatsApp group via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const payload: Record<string, unknown> = {
              subject: args.subject,
              participants: args.participants,
            };
            if (args.description) payload["description"] = args.description;
            const data = await client.post(`/group/create/${client.instanceName}`, payload);
            return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
          } catch (e) {
            if (e instanceof McpError) return { isError: true, content: [{ type: "text" as const, text: e.message }] };
            throw e;
          }
        }
      );
    }
  • Import of registerCreateGroup from create-group.ts
    import { registerCreateGroup } from "./create-group.js";
  • Call to registerCreateGroup(server, client) to wire up the tool during startup.
    registerCreateGroup(server, client);
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only says 'create a new WhatsApp group', which implies a write operation, but does not mention authentication requirements, potential side effects (e.g., consuming credits, creating on behalf of instance), or the group's initial state. Minimal information beyond the name.

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?

The description is a single sentence that front-loads the action. It is concise with no superfluous words. However, it could benefit from additional context without becoming verbose.

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?

Despite simplicity (3 params, no output schema), the description lacks completeness. It does not explain what happens on success (e.g., returns group ID), how errors are handled (e.g., invalid participants), or the requirement for an active instance. The description is too sparse for an agent to fully understand the tool's operation.

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%, so baseline is 3. The description adds no extra parameter semantics; it only restates the tool's purpose. The schema already describes each parameter adequately, so no deduction is needed.

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', the resource 'a new WhatsApp group', and the context 'via the pinned instance'. This distinguishes it from sibling tools that modify existing groups (e.g., update_group_subject) or invite to 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 is provided on when to use this tool versus alternatives. It does not specify that participants are required, or that this should be used only when the instance is authenticated and ready. No when-not-to-use or alternative suggestions are given.

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

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