buddyboss/list-group-members returns who belongs to a group, each with their role — admin, mod, member or banned — plus a count per role.
Call it before any membership change.
At a glance
| Ability | buddyboss/list-group-members |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Groups |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
BuddyBoss’s own route hides organizers and banned members. Hiding banned members is the consequential one: a hidden banned member is indistinguishable from somebody who was never in the group.
That matters because re-inviting them would undo a deliberate removal — a moderation decision reversed by somebody who had no way to know it existed.
So both are included here, and counted by role so the shape of the group is visible.
BuddyBoss tends to no-op rather than error when a write assumes a state that is not true. Banning somebody who is not a member, or promoting somebody who is already an organizer, succeeds and changes nothing — so reading the current state first is how you tell a successful write from a successful nothing.
Which is why this read is the step before every membership write. Banning a non-member and promoting an existing organizer both succeed and change nothing, and a successful nothing is indistinguishable from a successful something in the response.
The role names are worth knowing: BuddyBoss stores the top group role as admin and shows it as “Organizer” in the interface.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
group_id | integer | Yes | The group. |
role | string | No | Restrict to one role. |
per_page | integer | No | Rows per page. |
What comes back
| Name | Type | What it is |
|---|---|---|
members | array | Each member with their role. |
counts | object | How many in each role, banned included. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Who is in this group, and who runs it?
It resolves to one call:
{
"ability": "buddyboss/list-group-members",
"parameters": {
"group_id": 12
}
}Worth knowing
- Banned members are included — hiding them invites undoing a moderation decision.
- Organizers are included too, unlike the underlying route.
- Read this before any membership write; BuddyBoss no-ops rather than erroring.
adminis the role shown as “Organizer”.
Related abilities
- BuddyBoss Manage Group Membership — change a standing
- BuddyBoss Get Group — the group’s own member count
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category