manage_collections

Manage collections and their membership. Actions: list, get, create, update, delete, add_assets, remove_assets, add_models, remove_models. Args: - action: required operation (see above) - collection_id: required for get, update, delete, and membership changes - name: used for create (required) or update. (Note: there is no `description` field on /collections — the API doesn't accept it.) - thumbnail: optional asset_id for the collection thumbnail (update only) - asset_ids: required for add_assets and remove_assets - model_ids: required for add_models and remove_models - limit, page_token: pagination for list (default limit=20) - response_format: 'json' (default) or 'markdown' - team_id, project_id: required for OAuth callers Returns: collection metadata (JSON or markdown). list returns collection summaries; membership actions return the updated collection state or mutation result. Examples: - "List my collections" -> action="list" - "Create a collection for hero assets" -> action="create", name="Hero Assets" - "Add these assets to a collection" -> action="add_assets", collection_id="collection_xxx", asset_ids=["asset_1", "asset_2"] - "Remove these models from a collection" -> action="remove_models", collection_id="collection_xxx", model_ids=["model_1"] Don't use when: You need tag management. Prefer manage_assets or manage_models instead.

{
  "action": "create",
  "name": "Dragon Concept Art",
  "description": "All dragon-themed assets for the fantasy RPG project",
  "team_id": "team_abc123",
  "project_id": "proj_xyz789"
}

{
  "collection": {
    "id": "col_dragons",
    "name": "Dragon Concept Art",
    "description": "All dragon-themed assets for the fantasy RPG project"
  }
}