Collection tools
Collections organize assets into groups (folders). These tools let you browse, create, rename, move and delete collections, and file assets into or out of them.
get-collections
List all collections for the organization.
Parameters
None.
Response
| Field | Type | Description |
|---|---|---|
collections | array | List of collections |
collections[].id | string | Collection identifier |
collections[].name | string | Collection name |
collections[].itemCount | number | Number of assets in the collection |
collections[].createdAt | string | ISO date |
collections[].updatedAt | string | ISO date |
total | number | Total number of collections |
Example
{
"tool": "get-collections",
"arguments": {}
}
create-collection
Create a new collection (folder) for organizing assets. Pass parentId to create a sub-folder;
omit it for a root-level collection. Folders can be nested up to 5 levels deep.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Name of the new collection |
description | string | No | Optional description shown in the UI |
parentId | string | No | Id of an existing collection to nest this one under. Omit for a root-level collection |
Response
| Field | Type | Description |
|---|---|---|
success | boolean | Whether the collection was created |
collection.id | string | ID of the new collection |
collection.name | string | Name |
collection.parentId | string | null | Parent collection id, or null if root-level |
collection.createdAt | string | ISO date |
collection.updatedAt | string | ISO date |
message | string | Confirmation message |
Example
{
"tool": "create-collection",
"arguments": {
"name": "Summer Campaign 2026"
}
}
update-collection
Rename a collection or change its description. To move it to a different parent, use
move-collection instead.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
collectionId | string | Yes | Id of the collection to update |
name | string | No | New name |
description | string | No | New description |
At least one of name or description must be provided.
Example
{
"tool": "update-collection",
"arguments": {
"collectionId": "<collection id>",
"name": "Summer Campaign 2026 Final"
}
}
move-collection
Move a collection into a different parent folder, or to the root level. Rejected if it would create a cycle or exceed the maximum folder depth (5).
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
collectionId | string | Yes | Id of the collection to move |
parentId | string | null | No | New parent collection id, or null/omit to move it to the root level |
Example
{
"tool": "move-collection",
"arguments": {
"collectionId": "<collection id>",
"parentId": "<new parent id>"
}
}
delete-collection
Soft-delete a collection. The assets inside are not deleted; they are only unlinked from the folder and stay in the library. Any sub-folders are deleted too.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
collectionId | string | Yes | Id of the collection to delete |
Example
{
"tool": "delete-collection",
"arguments": {
"collectionId": "<collection id>"
}
}
add-asset-to-collection
File an existing asset into a collection. An asset lives in at most one collection, so this moves it if it was previously in another folder.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
collectionId | string | Yes | Id of the target collection |
assetId | string | Yes | Id of the asset to add (from get-assets) |
Example
{
"tool": "add-asset-to-collection",
"arguments": {
"collectionId": "<collection id>",
"assetId": "<asset id>"
}
}
remove-asset-from-collection
Remove an asset from a collection without deleting it. The asset stays in the library, just no longer filed in that folder.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
collectionId | string | Yes | Id of the collection the asset is currently in |
assetId | string | Yes | Id of the asset to remove from the folder |
Example
{
"tool": "remove-asset-from-collection",
"arguments": {
"collectionId": "<collection id>",
"assetId": "<asset id>"
}
}