Skip to main content
Glama
billyfranklim1

mcp-evolution

Send Group Invite

send_group_invite

Send a WhatsApp group invite link to specified contacts. Provide the group JID, an invite message, and recipient numbers.

Instructions

Send a WhatsApp group invite link to specific contacts via the pinned instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupJidYesGroup JID to invite people to
descriptionYesInvite message description
numbersYesPhone numbers or JIDs to send the invite to

Implementation Reference

  • The main handler that calls Evolution API POST /group/sendInvite/{instanceName} with groupJid, description, and numbers.
    export function registerSendGroupInvite(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "send_group_invite",
        {
          title: "Send Group Invite",
          description: "Send a WhatsApp group invite link to specific contacts via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const data = await client.post(`/group/sendInvite/${client.instanceName}`, {
              groupJid: args.groupJid,
              description: args.description,
              numbers: args.numbers,
            });
            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;
          }
        }
      );
  • Zod input schema defining required fields: groupJid, description, and numbers (array of phone numbers/JIDs).
    const schema = {
      groupJid: z.string().min(1).describe("Group JID to invite people to"),
      description: z.string().min(1).describe("Invite message description"),
      numbers: z.array(z.string().min(1)).min(1).describe("Phone numbers or JIDs to send the invite to"),
    };
  • Import of the send group invite registration function.
    import { registerSendGroupInvite } from "./send-group-invite.js";
  • Registration call that wires the send_group_invite tool into the MCP server during initialization.
    registerSendGroupInvite(server, client);
Behavior2/5

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

No annotations provided; description only says 'send invite link' but does not disclose side effects (e.g., whether link is auto-generated), permission requirements, rate limits, or error handling.

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?

Single sentence, front-loaded with action. Could be longer to add necessary detail, but no wasted words.

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 tool with 3 required parameters and no output schema, description lacks crucial context like return behavior, required permissions, and limitations.

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. Description adds no additional meaning beyond schema, but does not conflict with it.

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?

Description clearly states verb 'send', resource 'WhatsApp group invite link', and target 'specific contacts via pinned instance'. It distinguishes from sibling tools like accept_invite and fetch_invite_code.

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, no prerequisites mentioned (e.g., admin rights), no exclusions or preferred contexts.

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