buddyboss/delete-media deletes media items and their underlying files.
confirm_count must exactly equal the number of IDs you pass.
Before you run it
There is no trash: the items and their underlying files are gone. confirm_count must exactly equal the number of IDs you pass, which is how a mistyped or over-broad list gets caught before it runs. Deleting media that appeared in an activity post also removes it from that post, leaving a gap in somebody else’s content. To hide media instead, buddyboss/manage-media can set privacy to onlyme.
At a glance
| Ability | buddyboss/delete-media |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Media & Documents |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Destructive and permanent — deletes media and the underlying files. Requires confirm_count matching the number of IDs passed. |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
This is a bulk operation, which means the usual risk is not deleting the wrong item but deleting more items than intended — a list built from a query that matched too much.
A confirmation on each ID would be unusable at bulk scale, and a boolean confirmation says nothing about scale at all. Matching the count does: somebody who meant to delete three things and has built a list of three hundred finds out at the point of confirming.
The files go with the records. There is no trash and no recovery from within BuddyBoss — only a filesystem backup.
Media that appeared in an activity post is removed from that post as well, leaving a gap where the image was. That post may be somebody else’s, and they are not told.
Setting privacy to onlyme hides an item from everybody but its owner and is reversible, which covers most of what people actually want when they say remove.
Not idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
media_ids | array | Yes | The items to delete. |
type | string | Yes | photo, document or video. |
confirm_count | integer | Yes | Must exactly equal the number of IDs passed. |
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
deleted | array | The items removed. |
activity_gaps | integer | How many activity posts lost an attachment. |
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:
Delete those three uploaded images.
It resolves to one call:
{
"ability": "buddyboss/delete-media",
"parameters": {
"media_ids": [880, 881, 882],
"type": "photo",
"confirm_count": 3
}
}Worth knowing
- The count catches an over-broad list, which is the real risk at bulk scale.
- Files go too. Only a filesystem backup recovers them.
- Activity posts that used the media are left with a gap.
- Privacy
onlymeis the reversible alternative.
Related abilities
- BuddyBoss Manage Media — hide it instead
- BuddyBoss List Media — build the list carefully
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category