Skip to main content
Glama
liveblocks
by liveblocks

mark-thread-as-resolved

Mark a Liveblocks thread as resolved to close discussions and organize collaborative conversations in real-time applications.

Instructions

Mark a Liveblocks thread as resolved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomIdYes
threadIdYes
dataYes

Implementation Reference

  • The handler function that implements the core logic of the 'mark-thread-as-resolved' tool by invoking the Liveblocks SDK method via callLiveblocksApi.
    async ({ roomId, threadId, data }, extra) => { return await callLiveblocksApi( getLiveblocks().markThreadAsResolved( { roomId, threadId, data }, { signal: extra.signal } ) ); }
  • Zod input schema for the tool parameters: roomId (string), threadId (string), and data object with userId (string).
    { roomId: z.string(), threadId: z.string(), data: z.object({ userId: z.string(), }), },
  • src/server.ts:338-356 (registration)
    The server.tool() call that registers the 'mark-thread-as-resolved' tool with its name, description, schema, and handler function.
    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 } ) ); } );

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