buddyboss/manage-media organises photos and videos that already exist: moves them between albums, changes their privacy, renames them.
It cannot upload.
At a glance
| Ability | buddyboss/manage-media |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Media & Documents |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
Why uploading is not possible here
BuddyBoss requires attachment IDs that come from a binary multipart upload. A JSON call cannot perform one, so new files must be added through the site itself.
That is a protocol limitation rather than a policy decision, and it applies equally to avatars and documents.
What is possible is everything after the upload, which is most of the actual work on an established community: things end up in the wrong album, or with the wrong privacy, far more often than they need re-uploading.
Changing privacy to public makes an item visible beyond the community — unless it belongs to a group, in which case the group still governs. That exception is easy to forget and produces the belief that a privacy change did nothing.
Documents are handled by buddyboss/manage-document instead, because they nest in folders that inherit privacy rather than sitting in flat albums.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
media_id | integer | Yes | The photo or video. |
album_id | integer | No | Move it into this album. |
privacy | string | No | New privacy. A group still governs when the item is in one. |
title | string | No | Rename it. |
What comes back
| Name | Type | What it is |
|---|---|---|
media | object | The item after the write. |
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:
Move that photo into the events album.
It resolves to one call:
{
"ability": "buddyboss/manage-media",
"parameters": {
"media_id": 880,
"album_id": 14
}
}Worth knowing
- Uploading needs a binary multipart request a JSON call cannot make.
- A group overrides item privacy, so a privacy change there appears to do nothing.
- Documents use folders and a different ability.
- Idempotent.
Related abilities
- BuddyBoss Manage Album — the albums to move between
- BuddyBoss Get Media — check the effective visibility
- BuddyBoss Delete Media — remove it
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category