Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Get one group

get_group
Read-onlyIdempotent

Fetch a WhatsApp group: its name, description, picture and settings.

Returns how many participants it has, not who they are. Membership is not readable here: it arrives as it changes, on the group.participants_added / _removed / _promoted / _demoted events, which list_events can read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
group_idYesGroup id (`grp_…`), from `list_groups`. It belongs to the number you listed it under: passing it under a different number answers not found, which means wrong number rather than deleted.
number_aliasNoWhich of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.main

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / group_id / description
      Previous value: -"Group id (`grp_…`), from `list_groups`. It belongs to the number you listed it under: passing it under a different number answers not found, which means wrong inbox rather than deleted."New value: +"Group id (`grp_…`), from `list_groups`. It belongs to the number you listed it under: passing it under a different number answers not found, which means wrong number rather than deleted."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real behavioral context: the response contains a participant count but not identities, and that data is only available as change events. That is a limitation an agent could not infer from the annotations or schema and would otherwise be surprised by.

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 short blocks, zero filler: the first sentence defines the resource and returned fields, the second immediately qualifies the limitation and names the alternative. The most important caveat is front-loaded rather than buried.

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, return values need not be enumerated, and the description covers the one non-obvious gap (no participant list). It is slightly thin on failure behavior, though the group_id schema field already explains the cross-number "not found" case.

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 description coverage is 100% and both parameters are thoroughly documented in the schema (group_id format and cross-number failure semantics, number_alias resolution). The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 ("Fetch a WhatsApp group") plus the fields returned (name, description, picture, settings). The singular scope plus the explicit contrast with `list_events` for membership data lets an agent distinguish it from `list_groups` and other getters without opening a schema.

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?

Gives an explicit exclusion and an alternative: participants are not readable here, and `group.participants_added`/`_removed`/`_promoted`/`_demoted` via `list_events` is the way to observe membership changes. It does not cover other when-to-use cases (e.g. versus other group endpoints), but the one genuinely ambiguous need is routed correctly.

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.