Skip to main content
Glama
liveblocks

Liveblocks

Official
by liveblocks

get-thread

Retrieve a specific conversation thread from a Liveblocks room by providing both room and thread identifiers.

Instructions

Get a Liveblocks thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomIdYes
threadIdYes

Implementation Reference

  • The handler function for the 'get-thread' tool. It calls the Liveblocks client's getThread method via callLiveblocksApi, passing roomId and threadId, and handles the signal for cancellation.
    async ({ roomId, threadId }, extra) => {
      return await callLiveblocksApi(
        getLiveblocks().getThread({ roomId, threadId }, { signal: extra.signal })
      );
    }
  • Zod input schema defining parameters: roomId (string) and threadId (string).
    {
      roomId: z.string(),
      threadId: z.string(),
    },
  • src/server.ts:282-294 (registration)
    Registration of the 'get-thread' MCP tool using server.tool(), including name, description, input schema, and inline handler function.
    server.tool(
      "get-thread",
      "Get a Liveblocks thread",
      {
        roomId: z.string(),
        threadId: z.string(),
      },
      async ({ roomId, threadId }, extra) => {
        return await callLiveblocksApi(
          getLiveblocks().getThread({ roomId, threadId }, { signal: extra.signal })
        );
      }
    );
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states this is a 'Get' operation, implying read-only behavior, but doesn't disclose any behavioral traits like authentication requirements, rate limits, error conditions, or what data is returned. For a tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple retrieval tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't explain what a 'Liveblocks thread' is, what data is returned, or any behavioral context. For a tool in a complex collaboration system with many siblings, this minimal description leaves significant gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides no parameter information beyond what the schema shows (roomId and threadId). With 0% schema description coverage, the description doesn't compensate by explaining what these IDs represent, their format, or where to find them. However, since there are only 2 parameters and the tool name implies retrieval by ID, a baseline of 3 is appropriate despite the lack of added semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get') and resource ('a Liveblocks thread'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'get-threads' (plural) or 'get-thread-participants', but the verb+resource combination is specific enough for basic understanding.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get-threads' (list threads) and 'get-thread-participants' (get participants of a thread), the description offers no context about when this specific 'get-thread' operation is appropriate versus those other retrieval tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

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