Skip to main content
Glama

group_add_member

Add a member to an existing group on Telegram or WhatsApp.

What this does:

  • Adds the specified member to the group

  • Resolves the member by username, phone number, or JID

  • Reports if the member is already in the group

Returns: success, chat_id, member, already_member. On WhatsApp a person whose privacy settings forbid being added comes back success=false, error_type privacy, with invite_link to send them instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chat_id": "<chat_id>",
      "member": "<member>",
      "channel": "<channel>"
    },
    "name": "group_add_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
memberYesThe member to add (format depends on channel: @username on Telegram, phone on WhatsApp)
channelYesChannel where the group exists (e.g., 'telegram', 'whatsapp')
chat_idYesID of the group/channel to add the member to. Group id exactly as `group.list` reports it: a signed numeric id on Telegram, or a JID ending in @g.us on WhatsApp. A WhatsApp group has no numeric id, so this is a string either way. Read it from `group.list`; never compose one.
account_idNoWhich of the workspace's accounts on this channel acts (from channels.list). OMIT to use the account the group's conversation is filed on.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Which of the workspace's accounts on this channel acts (from channels.list). OMIT to use the account the group's conversation is filed on.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare it is non-read-only, non-destructive, and non-idempotent; the description adds real substance on top by naming the resolution formats, the `already_member` reporting behavior, and the concrete WhatsApp privacy failure mode with `error_type` and `invite_link`. It stops short of stating whether the acting account must itself be an admin or member, which is a meaningful gap for an add-to-group operation.

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 purpose sentence is front-loaded, followed by a short bullet list and a compact 'Returns' paragraph; there is no filler. The 'What this does:' header is slightly redundant given the bullets that follow, but the overall structure is clean and scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter mutation tool with no output schema, the description covers purpose, member resolution, returned fields, and the main failure mode, which is close to sufficient. Missing pieces are permission/admin prerequisites and whether a person must be a contact before being added.

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 schema already carries the parameter burden and baseline 3 applies. The description adds modest meaning by explaining that `member` is resolved by username, phone number, or JID, but it does not elaborate on `account_id` or `in_workspace` beyond what the schema states.

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 opens with a specific verb+resource ('Add a member to an existing group') and scopes it to Telegram or WhatsApp, so an agent knows exactly what operation it performs. It does not explicitly distinguish itself from the similarly named sibling `group_add`, leaving some ambiguity about which of the two to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrasing ('existing group') rather than stated: there is no explicit when-to-use versus when-not, and no mention of `group_add`, `group_join`, or `group_create` as alternatives. The WhatsApp privacy fallback (send `invite_link` instead) is a useful in-context guidance point that lifts it above a bare 2.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.