Create and manage named groups of documents and assets that cut across folders.
|
|
charmiq:// URI can belong to a Collection, regardless of where it lives in the user's folder hierarchy. Use them to group "the reading list for this project," "the assets the marketing Charm should know about," or any other ad-hoc set.https://api.charmiq.ai/mcp/collectionlist_collections | |
get_collection | charmiq:// URIs) |
create_collection | |
update_collection | |
delete_collection | |
add_to_collection | charmiq:// URI |
remove_from_collection | |
reorder_collection |
update_collection_item for editing per-item metadata used by the Docs and Homepage Collection uses.ordered flag:reorder_collection has no effect.reorder_collection. Use this when downstream consumers care about sequence (e.g. a homepage feed, a doc index).update_collection; the existing membership stays intact.charmiq:// URIs, not content. To act on a member, hand the URI to a tool on the VFS server:read_file to read contentdescribe_file for metadata and previewswrite_file, replace_string, apply_diff to editdelete_file to remove the underlying document (this also leaves a dangling reference in any Collection it was in — clean up with remove_from_collection)get_collection still returns the URI — the dangling reference is yours to handle.get_collection to read the current member list rather than caching it. The user can change Collections in the UI between your calls.update_collection_item only when you must. It's role-gated and used for system-level Collection uses (Docs, Homepage). A normal application doesn't need it.