Skip to main content
Glama
liveblocks
by liveblocks

unsubscribe-from-thread

Remove a user from notifications or updates for a specific thread in Liveblocks by providing the room ID, thread ID, and user ID.

Instructions

Unsubscribe from a Liveblocks thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
roomIdYes
threadIdYes

Implementation Reference

  • The main handler function that executes the unsubscribe-from-thread tool logic by calling the Liveblocks API via getLiveblocks().unsubscribeFromThread wrapped in callLiveblocksApi.
    async ({ roomId, threadId, data }, extra) => { return await callLiveblocksApi( getLiveblocks().unsubscribeFromThread( { roomId, threadId, data }, { signal: extra.signal } ) ); }
  • Zod schema defining the input parameters for the unsubscribe-from-thread tool: roomId, threadId, and data containing userId.
    { roomId: z.string(), threadId: z.string(), data: z.object({ userId: z.string(), }), },
  • src/server.ts:415-433 (registration)
    MCP server tool registration for 'unsubscribe-from-thread', including name, description, schema, and inline handler.
    server.tool( "unsubscribe-from-thread", "Unsubscribe from a Liveblocks thread", { roomId: z.string(), threadId: z.string(), data: z.object({ userId: z.string(), }), }, async ({ roomId, threadId, data }, extra) => { return await callLiveblocksApi( getLiveblocks().unsubscribeFromThread( { roomId, threadId, data }, { signal: extra.signal } ) ); } );

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/liveblocks/liveblocks-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server