Skip to main content
Glama
liveblocks
by liveblocks

mark-thread-as-resolved

Mark a specific thread as resolved in Liveblocks by specifying the room ID, thread ID, and user ID to manage thread status effectively.

Instructions

Mark a Liveblocks thread as resolved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
roomIdYes
threadIdYes

Implementation Reference

  • src/server.ts:338-356 (registration)
    Registration of the 'mark-thread-as-resolved' tool, including description, input schema, and handler function that calls the Liveblocks API.
    server.tool( "mark-thread-as-resolved", "Mark a Liveblocks thread as resolved", { roomId: z.string(), threadId: z.string(), data: z.object({ userId: z.string(), }), }, async ({ roomId, threadId, data }, extra) => { return await callLiveblocksApi( getLiveblocks().markThreadAsResolved( { roomId, threadId, data }, { signal: extra.signal } ) ); } );
  • Handler function executing the tool logic by calling Liveblocks' markThreadAsResolved via callLiveblocksApi utility.
    async ({ roomId, threadId, data }, extra) => { return await callLiveblocksApi( getLiveblocks().markThreadAsResolved( { roomId, threadId, data }, { signal: extra.signal } ) ); }
  • Zod input schema validating roomId, threadId, and data.userId parameters.
    { roomId: z.string(), threadId: z.string(), data: z.object({ userId: z.string(), }), },

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