WhatsMCP: MCP for WhatsApp

Get Group Invite Link

wa_get_group_invite_link

Get a WhatsApp group's invite link, or set reset=true to revoke it and issue a new one. The account must be a group admin.

Input Schema

TableJSON Schema

Name	Required	Description
`reset`	No	true to revoke the current link and issue a new one
`group_jid`	Yes	the group (…@g.us) JID, as returned by wa_list_groups
`account_id`	Yes	the account, as returned by wa_list_accounts

Output Schema

TableJSON Schema

Name	Required	Description
`items`	No	the rows of a list operation
`status`	Yes	ok (the operation succeeded) or refused (see refusal; for wa_update_group, applied lists the changes that took effect before it)
`applied`	No	wa_update_group only: the settings that were changed, in order — on a refusal, the ones that took effect before it
`refusal`	No	present only when status is refused
`summary`	No	a human-readable result
`group_jid`	No	the new group's JID (wa_create_group only) — use it as wa_send_message's 'to'
`invite_link`	No	the group's invite link (wa_create_group or wa_get_group_invite_link)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 22, 2026

addedOutput schema / properties / applied

Added value: +{
+  "description": "wa_update_group only: the settings that were changed, in order — on a refusal, the ones that took effect before it",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

changedOutput schema / properties / status / description

Previous value: -"ok (the operation succeeded) or refused (nothing was done)"New value: +"ok (the operation succeeded) or refused (see refusal; for wa_update_group, applied lists the changes that took effect before it)"

First observedSep 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations indicate no read-only or idempotent behavior, and the description correctly implies mutation (especially with reset=true). It adds important behavior: revoking the link with reset=true and the admin requirement. However, it doesn't disclose what happens to the old link (e.g., is it invalidated immediately?) or whether the reset is reversible, but given annotations provide the baseline this is sufficient context.

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 description is a single clear sentence with the essential info front-loaded. It includes the key behavioral nuance (reset) and a requirement (admin). No filler. Slightly more context could be added about return value, but it's appropriately brief.

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?

The tool is simple with only 3 params, full schema coverage, and an output schema (though not detailed here). The description covers the primary use case and the reset option. Missing details like the shape of the invite link response are covered by the output schema. Overall, it's complete enough for an agent to invoke correctly.

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 coverage is 100%, and the description doesn't add much beyond the schema's own parameter descriptions. It mentions reset=true but that's already in the schema. The description does reinforce that group_jid and account_id come from wa_list_groups and wa_list_accounts, which is a subtle addition, but not significant. Baseline 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 clearly identifies the tool's purpose: to retrieve a group invite link, with an optional reset behavior. It specifies the resource (WhatsApp group) and the action (get/set invite link), and distinguishes it from siblings like wa_join_group or wa_update_group by focusing on the invite link specifically.

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?

The description implies when to use it: when needing to obtain or reset an invite link. It doesn't explicitly mention alternatives or when not to use it, but the context is clear given the sibling list. The requirement of admin privileges is a useful usage condition, though it doesn't elaborate on scenarios like 'use this instead of wa_update_group'.

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

All WhatsMCP: MCP for WhatsApp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?