buddyboss/list-members searches and pages the member directory, returning each member’s ID, name, login, avatar and last activity.
The scope you choose changes the answer more than it looks.
At a glance
| Ability | buddyboss/list-members |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Members & Connections |
| 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
Alphabetical — the default — and newest, by registration date, always return every member. They are based on facts every account has.
The other three are not. active orders by last activity, online lists members seen in the last few minutes, and popular ranks by connection count. Every one of them can legitimately return nothing on a quiet community, or on one where the relevant component is switched off.
A zero from those scopes reads as “this community has no members”, which is why the response says so explicitly and reports the real member count alongside.
The search filter matches both name and login. Login matters because display names are not unique on a BuddyBoss site and two people can legitimately share one.
member_type restricts to one profile type, and the valid slugs come from buddyboss/list-community-taxonomies — an unrecognised one is usually ignored rather than rejected, which produces an unfiltered list that looks filtered.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
search | string | No | Matches name and login. |
type | string | No | Scope: alphabetical, newest, active, online or popular. |
member_type | string | No | Restrict to one profile type. |
per_page | integer | No | Rows per page. |
page | integer | No | Page number. |
What comes back
| Name | Type | What it is |
|---|---|---|
members | array | Each member with ID, name, login, avatar and last activity. |
total | integer | How many matched. |
scope_note | string | A warning when an engagement scope returned little or nothing. |
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 community?
It resolves to one call:
{
"ability": "buddyboss/list-members",
"parameters": {
"per_page": 50
}
}Worth knowing
- Alphabetical and newest always work; the engagement scopes may not.
- Display names are not unique. Login is.
- An unrecognised member type is ignored, producing an unfiltered list.
- Read-only.
Related abilities
- BuddyBoss Get Member — one member in full
- BuddyBoss List Community Taxonomies — the valid member type slugs
- BuddyBoss Manage Member — change one
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category