Liveblocks
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIVEBLOCKS_SECRET_KEY | Yes | Your Liveblocks secret key from a project in your dashboard |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-roomsC | Get recent Liveblocks rooms |
| create-roomC | Create a Liveblocks room |
| get-roomC | Get a Liveblocks room |
| update-roomB | Update a Liveblocks room |
| delete-roomC | Delete a Liveblocks room |
| update-room-idC | Update a Liveblocks room's ID |
| get-active-usersC | Get a Liveblocks room's active users |
| broadcast-eventC | Broadcast an event to a Liveblocks room |
| get-storage-documentC | Get a Liveblocks storage document |
| get-yjs-documentC | Get a Liveblocks Yjs text document |
| get-threadsC | Get recent Liveblocks threads |
| create-threadC | Create a Liveblocks thread. Always ask for a userId. |
| get-threadC | Get a Liveblocks thread |
| get-thread-participantsC | Get a Liveblocks thread's participants |
| edit-thread-metadataC | Edit a Liveblocks thread's metadata. |
| mark-thread-as-resolvedC | Mark a Liveblocks thread as resolved |
| mark-thread-as-unresolvedB | Mark a Liveblocks thread as unresolved |
| delete-threadC | Delete a Liveblocks thread |
| subscribe-to-threadC | Subscribe to a Liveblocks thread |
| unsubscribe-from-threadC | Unsubscribe from a Liveblocks thread |
| get-thread-subscriptionsC | Get a Liveblocks thread's subscriptions |
| create-commentC | Create a Liveblocks comment. Always ask for a userId. |
| get-commentC | Get a Liveblocks comment |
| edit-commentC | Edit a Liveblocks comment |
| delete-commentC | Delete a Liveblocks comment |
| add-comment-reactionC | Add a reaction to a Liveblocks comment |
| remove-comment-reactionC | Remove a reaction from a Liveblocks comment |
| get-room-subscription-settingsC | Get a Liveblocks room's subscription settings |
| update-room-subscription-settingsC | Update a Liveblocks room's subscription settings |
| delete-room-subscription-settingsC | Delete a Liveblocks room's subscription settings |
| get-user-room-subscription-settingsC | Get a user's room subscription settings |
| get-inbox-notificationsC | Get recent Liveblocks inbox notifications |
| get-inbox-notificationC | Get a Liveblocks inbox notification |
| trigger-inbox-notificationC | Create a custom Liveblocks inbox notification |
| delete-inbox-notificationC | Delete a Liveblocks inbox notification |
| delete-all-inbox-notificationsC | Delete all Liveblocks inbox notifications |
| get-notification-settingsC | Get a Liveblocks notification settings |
| update-notification-settingsC | Update Liveblocks notification settings |
| delete-notification-settingsC | Delete Liveblocks notification settings |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 39 tools
Most tools have distinct purposes targeting specific resources like rooms, comments, threads, notifications, and storage. However, some potential overlap exists between get-room and get-rooms, or between various notification-related tools, but descriptions clarify their scope. The set is well-organized by resource type, making tool selection generally clear.
All tools use a consistent kebab-case verb-noun pattern throughout, such as create-room, get-thread, update-notification-settings. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 39 tools, the count feels heavy for a collaborative platform server, potentially overwhelming for agents. While Liveblocks has multiple features (rooms, comments, threads, notifications, storage), the tool set could be more streamlined, as some operations like get-room and get-rooms might be consolidated or grouped.
The tool set provides comprehensive CRUD and lifecycle coverage across all major Liveblocks domains: rooms, comments, threads, notifications, and storage. It includes creation, retrieval, updating, deletion, and specialized actions like reactions and subscriptions, leaving no obvious gaps for agent workflows.