Skip to main content
Glama
ExoCubeYT

OpenWA MCP Server

by ExoCubeYT

add_group_member

Add a new member to a WhatsApp group by specifying the session, group, and participant phone IDs.

Instructions

Add a participant to a WhatsApp group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID
groupIdYesGroup ID
participantIdYesPhone ID of the participant to add

Implementation Reference

  • The handler function for 'add_group_member' tool. Sends a POST request to /sessions/{sessionId}/groups/{groupId}/members with the participantId in the body.
    async ({ sessionId, groupId, participantId }) => {
      const data = await openwaClient({
        method: "POST",
        path: `/sessions/${sessionId}/groups/${groupId}/members`,
        body: { participantId },
      });
      return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
    }
  • The schema definition for 'add_group_member' tool. Defines description and inputSchema with sessionId (string), groupId (string), and participantId (string).
    {
      description: "Add a participant to a WhatsApp group",
      inputSchema: {
        sessionId: z.string().describe("Session ID"),
        groupId: z.string().describe("Group ID"),
        participantId: z.string().describe("Phone ID of the participant to add"),
      },
    },
  • Registration of 'add_group_member' tool via server.registerTool() inside the registerGroupTools function.
    server.registerTool(
      "add_group_member",
      {
        description: "Add a participant to a WhatsApp group",
        inputSchema: {
          sessionId: z.string().describe("Session ID"),
          groupId: z.string().describe("Group ID"),
          participantId: z.string().describe("Phone ID of the participant to add"),
        },
      },
      async ({ sessionId, groupId, participantId }) => {
        const data = await openwaClient({
          method: "POST",
          path: `/sessions/${sessionId}/groups/${groupId}/members`,
          body: { participantId },
        });
        return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
      }
    );
  • src/index.ts:18-18 (registration)
    The registerGroupTools(server) call that wires up all group tools including add_group_member.
    registerGroupTools(server);
  • The openwaClient helper function used by the handler to make HTTP requests to the OpenWA API.
    export async function openwaClient<T = unknown>(opts: RequestOptions): Promise<T> {
      const url = `${BASE_URL}${opts.path}`;
    
      const headers: Record<string, string> = {
        "Content-Type": "application/json",
        "X-API-Key": API_KEY,
      };
    
      const res = await fetch(url, {
        method: opts.method,
        headers,
        body: opts.body ? JSON.stringify(opts.body) : undefined,
      });
    
      const text = await res.text();
    
      if (!res.ok) {
        throw new Error(`OpenWA API ${res.status}: ${text}`);
      }
    
      try {
        return JSON.parse(text) as T;
      } catch {
        return text as T;
      }
    }
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that adding a member typically requires admin privileges, whether notifications are sent, or error scenarios (e.g., group full, member already exists).

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

Conciseness3/5

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

The description is a single short sentence, which is concise but lacks structure. It is not verbose, but could include key additional context in a similarly concise form (e.g., permissions, side effects).

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 the tool is a mutation operation with no output schema and no annotations, the description is incomplete. It leaves out important context such as required permissions, side effects, and error handling.

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 the baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions, but the schema itself is clear enough. No further elaboration 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 'Add' and the resource 'participant to a WhatsApp group', directly distinguishing it from sibling tools like 'create_group' (creates group) and 'remove_group_member' (removes member).

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 like 'promote_member' or 'demote_member'. No mention of prerequisites (e.g., admin status) or context for how adding a member differs from creating a 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/ExoCubeYT/openwa-mcp'

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