No user-submitted related servers found.
Scored across 14 tools
Most tools map to a distinct resource and action, with clear separation between event CRUD, upload flows, analytics, and account/usage. The main ambiguity is get_event vs get_event_analytics, since both report guest visits and selfie searches, and get_usage vs get_account_info are both account-level but cover different data.
All 14 tools follow a consistent snake_case verb_noun pattern: get_*, create_*, list_*, update_*, delete_*, restore_*, and upload_photos_from_*. Composite names like get_event_qr and get_event_analytics fit the same predictable style without mixing conventions.
14 tools is well within the ideal range for an event/gallery management server, and each tool has a clear operational purpose. The count feels complete without being bloated: usage, account context, event lifecycle, upload entry points, analytics, and QR access are all covered.
Event CRUD is thoroughly covered including soft-delete and restore, and uploads are supported via local paths, URLs, Drive, and a no-login link. The notable gap is direct per-photo management—listing, removing, or editing individual photos after upload—but agents can work around it through the gallery URL and upload link.
