Skip to main content
Glama

Read a WhatsApp group

get_group
Read-onlyIdempotent

Read one of the user's WhatsApp groups as it is now: its name, whether everyone or only admins may send messages, the role of the user's number (member, admin or owner), every participant with their phone and role, and the invite link when the user's number is an admin and this connection may act for the user. Call it before changing a group, to know who is in it and whether the number may change it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNoThe connected number, from list_connected_numbers. Omit it when the user has a single connected number.
chat_idNoThe group, by the chat_id list_capturable_chats returns. Name the group by its chat_id from list_capturable_chats, or by its name as chat_name; pass one of them.
chat_nameNoThe group, by its name exactly as list_capturable_chats returns it. Name the group by its chat_id from list_capturable_chats, or by its name as chat_name; pass one of them.

Output Schema

NameRequiredDescriptionDefault
nameNo
chat_idNoThe group's chat_id.
invite_linkNoThe group's invite link, present when the user's number is an admin and this connection may act for the user.
number_roleNoThe user's number in the group: "member", "admin" or "owner". Only an admin or the owner can change the group.
participantsNoEveryone in the group.
who_can_sendNo"everyone", or "admins" when only admins may send messages.
conversation_idNoThe captured conversation of this group, when it is captured.
conversation_urlNoWhere a person opens that conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that the response reflects current state and that the invite link is returned only when the user's number is an admin and the connection may act for the user. That permission-sensitive condition is exactly the kind of behavioral context annotations cannot convey.

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?

Two sentences, front-loaded with the resource and its returned fields, then the usage condition. The list of returned fields is dense but every clause carries information an agent needs; there is no filler.

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?

For a read-only, three-parameter tool with full schema coverage, annotations, and an output schema, the description covers scope, returned fields, permission-conditional behavior, and when to call it. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so phone, chat_id, and chat_name are already documented, including the either/or rule between chat_id and chat_name. The description adds no parameter meaning beyond the schema, but with complete schema documentation a baseline is appropriate; it does not mislead or omit anything.

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 gives a specific verb (read) and resource (one of the user's WhatsApp groups) and enumerates the exact fields returned: name, messaging policy, the user's role, participants with phone and role, and the conditional invite link. It is highly specific, but it never names or distinguishes itself from a sibling read tool such as get_conversation.

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 clear when-to-use guidance: call it before changing a group, to learn membership and whether the number may change it. It does not name an alternative tool or state exclusions, so it falls short of full when/when-not guidance.

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.

Resources