buddyboss/get-thread returns a message thread with its messages in chronological order, oldest first.
BuddyBoss returns them newest-first, which reads a conversation backwards.
At a glance
| Ability | buddyboss/get-thread |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Messages |
| 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
That reordering is a small thing that matters a lot. A conversation read newest-first is a sequence of replies to context that has not arrived yet, and for anything summarising or reasoning about a thread it is actively misleading.
Reading another member’s private correspondence is permitted here because administrators hold bp_moderate. It is still somebody’s private correspondence, and the response names every participant so it is clear whose messages were opened.
The participant list is returned in full rather than as a count, which is the point: “opened a thread” and “opened a thread between these four people” are different records of the same action.
There is no editing of messages. A sent message is a record of what somebody said, and BuddyBoss offers no route to change one — which is the right behaviour and is worth knowing before planning around it.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
thread_id | integer | Yes | The thread. |
user_id | integer | No | Whose view of the thread to read. |
What comes back
| Name | Type | What it is |
|---|---|---|
thread | object | The thread with its participants. |
messages | array | The messages, oldest first. |
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:
Show me that message thread.
It resolves to one call:
{
"ability": "buddyboss/get-thread",
"parameters": {
"thread_id": 512
}
}Worth knowing
- Reordered to oldest-first. BuddyBoss returns the opposite.
- Participants are named in full, deliberately.
- Messages cannot be edited — there is no route for it.
- Read-only.
Related abilities
- BuddyBoss List Message Threads — find the thread ID
- BuddyBoss Send Message — reply into it
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category