Skip to main content
Glama
liveblocks

Liveblocks

Official
by liveblocks

get-thread-participants

Retrieve participant information from a specific Liveblocks thread to identify users engaged in collaborative discussions.

Instructions

Get a Liveblocks thread's participants

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomIdYes
threadIdYes

Implementation Reference

  • Handler function that executes the get-thread-participants tool by invoking the Liveblocks client's getThreadParticipants method via callLiveblocksApi.
    async ({ roomId, threadId }, extra) => {
      return await callLiveblocksApi(
        getLiveblocks().getThreadParticipants(
          { roomId, threadId },
          { signal: extra.signal }
        )
      );
    }
  • Zod input schema defining parameters: roomId (string) and threadId (string).
    {
      roomId: z.string(),
      threadId: z.string(),
    },
  • src/server.ts:296-311 (registration)
    Registration of the 'get-thread-participants' tool on the McpServer instance, including description, input schema, and handler function.
    server.tool(
      "get-thread-participants",
      "Get a Liveblocks thread's participants",
      {
        roomId: z.string(),
        threadId: z.string(),
      },
      async ({ roomId, threadId }, extra) => {
        return await callLiveblocksApi(
          getLiveblocks().getThreadParticipants(
            { 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 format the participants data returns in. This leaves significant gaps for an agent to understand how to use it effectively.

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, clear sentence that gets straight to the point with no wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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, 0% schema coverage, and no output schema, the description is insufficiently complete. For a tool with 2 required parameters that retrieves participant data, it should explain parameter meanings, return format, and any constraints. The current description leaves too much undefined for effective agent use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'thread' and 'participants' but doesn't explain what 'roomId' and 'threadId' parameters represent, their expected formats, or how they relate to retrieving participants. The description adds minimal semantic value beyond the parameter names themselves.

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's participants'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get-thread' or 'get-threads', which also retrieve thread-related information but focus on different aspects.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get-thread' (for thread metadata) and 'get-threads' (for multiple threads), there's no indication of how this tool differs or when it's the appropriate choice.

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