wazap-mcp

Get WhatsApp group info

get_group_info

Read-onlyIdempotent

Retrieve complete WhatsApp group details including name, description, owner, participants up to 500, admin status, settings, community, and invite link. Use it before managing a 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

TableJSON Schema

Name	Required	Description	Default
`group_id`	Yes	<id>@g.us
`account_id`	No	Account id

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`owner`	Yes
`chat_id`	Yes
`community`	No
`account_id`	Yes
`created_at`	Yes
`i_am_admin`	Yes
`description`	Yes
`info_locked`	Yes
`invite_link`	No
`participants`	Yes
`join_approval`	Yes
`member_add_mode`	Yes
`announcement_only`	Yes
`participant_count`	Yes
`disappearing_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.0.3Sep 23, 2026

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"
+}

Changed1 schema field changedv0.15.0Sep 12, 2026

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"
+}

First observedv0.9.3Aug 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by specifying the conditional nature of the invite link ('for an admin') and the participant limit (up to 500), which are behavioral details not captured in annotations. It does not contradict annotations.

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

Conciseness5/5

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

The description is a single sentence that front-loads the key data returned, then appends a usage instruction. Every phrase earns its place, with no filler. It is concise yet complete.

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

Completeness5/5

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

Given the output schema exists and annotations cover read-only/idempotent behavior, the description covers what the tool returns, when to use it, and a sequencing note. Nothing essential is missing for an agent to correctly invoke this tool.

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?

The schema description coverage is 100%, with both group_id and account_id documented. The description does not add extra meaning beyond the schema—it mentions group info but not parameter-specific syntax or constraints. With full schema coverage, the baseline of 3 is appropriate.

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 states a specific verb ('get') and resource ('group info'), then enumerates the exact fields returned (name, description, owner, participants, admin status, settings, community, invite link). It clearly distinguishes itself from sibling tools like manage_group and get_status by listing what it retrieves and by the explicit 'Call it before manage_group' directive.

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

Usage Guidelines5/5

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

The description explicitly says 'Call it before manage_group,' giving a clear precondition and usage context. This directly tells an agent when to invoke this tool versus alternatives, leaving no ambiguity about sequencing.

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