Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Get WhatsApp group info

get_group_info
Read-onlyIdempotent

Retrieves a WhatsApp group's details—name, description, owner, participants, admin status, settings, community, and admin invite link—so you can review it before managing the group.

Instructions

A group's name, description, owner and participants (up to 500), whether the account is admin, its settings (info_locked, member_add_mode, join_approval, disappearing_seconds), its community, and the invite link for an admin. Call it before manage_group.

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": {
      "group_id": "<group_id>"
    },
    "name": "get_group_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes<id>@g.us
account_idNo

Output Schema

NameRequiredDescriptionDefault
nameYes
ownerYes
chat_idYes
communityNo
account_idYes
created_atYes
i_am_adminYes
descriptionYes
info_lockedYes
invite_linkNo
participantsYes
join_approvalYes
member_add_modeYes
announcement_onlyYes
participant_countYes
disappearing_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
  3. Changed3 schema fields changedv1.0.3
    • changedInput schema / properties / account_id / description
      Previous value: -"Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account."New value: +"Account id"
    • changedInput schema / properties / group_id / description
      Previous value: -"Group chat id (\"<id>@g.us\")"New value: +"<id>@g.us"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "account_id": {
      +      "type": "string"
      +    },
      +    "announcement_only": {
      +      "type": "boolean"
      +    },
      +    "chat_id": {
      +      "type": "string"
      +    },
      +    "community": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "is_community": {
      +          "type": "boolean"
      +        },
      +        "parent_group_id": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "is_community",
      +        "parent_group_id"
      +      ],
      +      "type": "object"
      +    },
      +    "created_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "description": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "disappearing_seconds": {
      +      "type": "number"
      +    },
      +    "i_am_admin": {
      +      "type": "boolean"
      +    },
      +    "info_locked": {
      +      "type": "boolean"
      +    },
      +    "invite_link": {
      +      "type": "string"
      +    },
      +    "join_approval": {
      +      "type": "boolean"
      +    },
      +    "member_add_mode": {
      +      "enum": [
      +        "admins",
      +        "all"
      +      ],
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "owner": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "participant_count": {
      +      "type": "number"
      +    },
      +    "participants": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "contact_id": {
      +            "type": "string"
      +          },
      +          "is_admin": {
      +            "type": "boolean"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "contact_id",
      +          "name",
      +          "is_admin"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "chat_id",
      +    "name",
      +    "description",
      +    "owner",
      +    "created_at",
      +    "participant_count",
      +    "participants",
      +    "announcement_only",
      +    "i_am_admin",
      +    "info_locked",
      +    "member_add_mode",
      +    "join_approval",
      +    "disappearing_seconds",
      +    "account_id"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changedv0.15.0
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  5. First observedv0.9.3

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds genuinely non-obvious behavior: the 500-participant cap (a truncation limit the agent must account for) and the fact that the invite link is only returned for admins (a privilege-conditional field). Those two facts are exactly the kind of thing annotations cannot express.

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?

It is a single compact sentence with no filler, and the ordering instruction is placed at the end where it reads as an afterthought. Most of the sentence is a field inventory that largely duplicates the output schema, so the word budget is spent on the least load-bearing content.

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

Completeness3/5

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

With an output schema present, enumerating return fields was not required, and the description spends nearly all its text there while leaving account_id and failure modes (group not found, not a participant) unexplained. The one thing it does uniquely well — the pre-manage_group ordering and the admin-only invite link — is buried. Adequate for a simple two-parameter read, but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: group_id carries the "<id>@g.us" format hint, but account_id is undocumented in both schema and description. The description says nothing about either parameter — not what account_id selects, not whether it defaults, and not the required group_id format — so it fails to compensate for the coverage gap.

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 enumerates exactly what is retrieved: group name, description, owner, participants (capped at 500), admin status, settings, community, and admin invite link. That is specific enough to distinguish it from manage_group, which is named directly. It is a noun-phrase inventory rather than a verb+resource statement, but the title supplies the verb and there is no ambiguity about the resource.

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

Usage Guidelines4/5

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

"Call it before manage_group" gives explicit ordering guidance relative to the one sibling that matters, which is the key routing decision for this tool. There is no statement of when not to call it or what happens if the account is not a member, so it stops short of full when/when-not coverage.

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