Skip to main content
Glama
liveblocks

Liveblocks

Official
by liveblocks

get-thread-subscriptions

Retrieve subscription details for a specific thread in a Liveblocks room to monitor user notifications and engagement.

Instructions

Get a Liveblocks thread's subscriptions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomIdYes
threadIdYes

Implementation Reference

  • The handler function for the 'get-thread-subscriptions' tool. It calls the Liveblocks API's getThreadSubscriptions method wrapped in callLiveblocksApi.
    async ({ roomId, threadId }, extra) => {
      return await callLiveblocksApi(
        getLiveblocks().getThreadSubscriptions(
          { roomId, threadId },
          { signal: extra.signal }
        )
      );
    }
  • Input schema defining parameters: roomId (string) and threadId (string).
    {
      roomId: z.string(),
      threadId: z.string(),
    },
  • src/server.ts:435-450 (registration)
    Registration of the 'get-thread-subscriptions' tool using McpServer.tool, including name, description, input schema, and inline handler.
    server.tool(
      "get-thread-subscriptions",
      "Get a Liveblocks thread's subscriptions",
      {
        roomId: z.string(),
        threadId: z.string(),
      },
      async ({ roomId, threadId }, extra) => {
        return await callLiveblocksApi(
          getLiveblocks().getThreadSubscriptions(
            { 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 'subscriptions' entail (e.g., user lists, notification settings). This leaves significant gaps for an agent to understand how to invoke it safely.

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 that directly states the tool's function without unnecessary words. It's front-loaded with the core purpose, making it easy to parse, though its brevity contributes to gaps in other dimensions.

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 the complexity (a read operation with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'subscriptions' are, how results are returned, or any prerequisites, leaving the agent with insufficient context to use the tool effectively.

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 for undocumented parameters. It mentions 'a Liveblocks thread's subscriptions', which implies 'threadId' is needed, but doesn't explain 'roomId' or clarify the relationship between room and thread. No parameter details are provided, failing to add meaning beyond the bare schema.

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 verb ('Get') and resource ('a Liveblocks thread's subscriptions'), making the purpose unambiguous. However, it doesn't distinguish this tool from similar siblings like 'get-thread' or 'get-thread-participants', which also retrieve thread-related data 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-thread-participants' (for participants), there's no indication of how 'subscriptions' differ or when this specific retrieval is appropriate, leaving usage context unclear.

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