buddyboss/get-community-report returns aggregate figures: how many members, how many are active, how many groups and of what privacy, how much activity and of what kind.
Everything is computed live from the same tables the directories read.
At a glance
| Ability | buddyboss/get-community-report |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Orientation & Reporting |
| 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 stores no analytics history. These are current figures, and there is no way to ask what they were last month — so tracking a community over time means recording these somewhere yourself.
The active-member figure is the one to read carefully. It depends on recorded activity, which means a site with activity feeds switched off reports very few active members while being perfectly healthy.
That caveat is attached to the section rather than left implicit, because a low active-member count reads as a dying community and can mean nothing of the sort.
Group counts by privacy are the most directly useful part. A community whose groups are overwhelmingly hidden behaves very differently from one whose groups are public, and the split says more about how the site is used than the total does.
Computed live means it costs real queries on a large community. It is not a cached dashboard.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
sections | array | No | Only compute these sections. |
What comes back
| Name | Type | What it is |
|---|---|---|
members | object | Total and active member counts, with their caveats. |
groups | object | Group counts by privacy status. |
activity | object | Activity counts by kind. |
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:
How big is this community?
It resolves to one call:
{
"ability": "buddyboss/get-community-report",
"parameters": {}
}Worth knowing
- No history is stored. Record these yourself to track over time.
- Active members depends on activity being recorded at all.
- Group privacy split says more than the total.
- Computed live — it costs queries on a large site.
Related abilities
- BuddyBoss Get Community Overview — what is switched on
- BuddyBoss List Members — the members behind the numbers
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category