Skip to main content
Glama

Listar grupos WhatsApp

list_whatsapp_groups
Read-only

Grupos WhatsApp do workspace com membros, o máximo de pessoas (o da campanha), se está trancado para novos membros, se é destino, ativo, saúde, incidentes abertos e as campanhas vinculadas. O link de convite completo só aparece com permissão de escrita (bot:write); sem ela vem mascarado. Use para "quais grupos estão lotados/com problema" ou para ver os grupos de uma campanha (campanha_id). Pagina com limite/offset: com has_more true, repita com offset = next_offset.

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": "list_whatsapp_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNoMáximo de grupos (1 a 200; padrão 50).
offsetNoQuantos itens pular (0 = início). Para a próxima página, use o next_offset da resposta.
campanha_idNoOpcional. Só os grupos vinculados a essa campanha (id ou slug).
so_com_problemaNoSe true, só grupos com problema: saúde ruim, inativo, lotado ou com incidente aberto.

Output Schema

NameRequiredDescriptionDefault
itensNoGrupos WhatsApp.
totalNoQuantos casaram com o filtro (todas as páginas).
successNo
has_moreNotrue quando há mais itens depois desta página.
next_offsetNooffset da próxima página; null na última.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive/closed-world, so the description's job is to add what annotations cannot. It does: the invite link is masked unless the caller holds bot:write, and pagination requires looping with has_more/next_offset. Those are exactly the operational facts an agent needs before calling.

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 first sentence is a long but information-dense enumeration of returned fields; the permission caveat, the use cases, and the pagination rule follow in tight order with no filler. No sentence is wasted, though the field list could be trimmed for faster scanning.

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?

Because an output schema exists, return values need not be explained, and the description covers the two things the schema cannot: permission-gated field masking and the pagination loop. For a read-only, 4-parameter filtered list tool this is sufficient to call it correctly.

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 the baseline is 3; the description goes beyond it by explaining the pagination contract (has_more true → repeat with offset = next_offset) and by noting campanha_id accepts an id or a slug. It does not restate the so_com_problema logic beyond what the schema already documents.

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?

States a specific verb and resource ('list_whatsapp_groups' → grupos WhatsApp do workspace) and enumerates the returned attributes: membros, máximo de pessoas, trancado, destino, ativo, saúde, incidentes, campanhas. It also disambiguates from siblings such as list_campaigns by noting the campanha_id filter path to reach a campaign's groups.

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?

Explicitly names the situations to use it: "quais grupos estão lotados/com problema" (amplified by the so_com_problema param) and viewing the groups of a campaign via campanha_id. It gives clear positive triggers but never states when NOT to use it or names a concrete alternative sibling to prefer.

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