Skip to main content
Glama
razvangirgiz

wazap-mcp

by razvangirgiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Get WhatsApp group info

get_group_info
Read-onlyIdempotent

Retrieve a WhatsApp group's name, description, owner, participants, admin status, settings, community, and admin invite link 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.

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. Changed1 schema field changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
  2. 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"
+}
  3. 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"
+}
  4. First observedv0.9.3

TDQS

A3.7/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, and the description adds useful context beyond them: a 500-participant cap and the fact that the invite link is only returned for an admin (an auth-conditional detail). It does not discuss pagination or failure modes, but the added constraints are valuable.

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?

It fits the essential information into one dense sentence with no wasted words, and the sequencing cue lands at the end. It reads as a return-value list rather than a front-loaded purpose statement, but nothing is superfluous.

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?

With an output schema present, the return enumeration is technically redundant but helpful, and annotations cover the safety profile. The only real gap is the unexplained account_id, but otherwise an agent has enough to call it correctly.

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?

At 50% schema coverage, only group_id is documented ('<id>@g.us') while account_id is undocumented in both schema and description. The description adds no parameter meaning to compensate, leaving account_id's role ambiguous from the definition alone.

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 the tool returns (name, description, owner, participants, settings, community, invite link), making the retrieval purpose clear. It also implies a read-only scope distinct from manage_group. It never quite states a leading verb, but an agent knows what it gets back.

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?

It gives an explicit sequencing rule: 'Call it before manage_group,' which tells the agent when this precedes a mutation. It does not name alternatives or when-not conditions, but the primary usage context is clear.

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

Deploy Server

Other Tools