Skip to main content
Glama
liveblocks

Liveblocks

Official
by liveblocks
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

update-room-id

Change a Liveblocks room's identifier to manage collaborative spaces by providing the current and new room IDs.

Instructions

Update a Liveblocks room's ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomIdYes
newRoomIdYes

Implementation Reference

  • src/server.ts:145-160 (registration)
    Registers the 'update-room-id' tool, including schema and inline handler function that wraps the Liveblocks client's updateRoomId method.
    server.tool(
  "update-room-id",
  "Update a Liveblocks room's ID",
  {
    roomId: z.string(),
    newRoomId: z.string(),
  },
  async ({ roomId, newRoomId }, extra) => {
    return await callLiveblocksApi(
      getLiveblocks().updateRoomId(
        { currentRoomId: roomId, newRoomId },
        { signal: extra.signal }
      )
    );
  }
);
  • src/server.ts:152-159 (handler)
    The handler function executes the tool logic by calling the Liveblocks updateRoomId API through callLiveblocksApi and getLiveblocks().
    async ({ roomId, newRoomId }, extra) => {
  return await callLiveblocksApi(
    getLiveblocks().updateRoomId(
      { currentRoomId: roomId, newRoomId },
      { signal: extra.signal }
    )
  );
}
  • src/server.ts:148-151 (schema)
    Input schema defining parameters: roomId (current room ID) and newRoomId (new room ID).
    {
  roomId: z.string(),
  newRoomId: z.string(),
},

Tool Definition Quality

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation (implying mutation), but doesn't disclose critical traits: whether this requires specific permissions, if it's reversible, what happens to existing room data, rate limits, or error conditions. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 maximally concise with a single clear sentence that front-loads the essential action. There's no wasted verbiage or redundancy. Every word earns its place by specifying the exact operation.

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 this is a mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't address what the tool returns, error conditions, side effects, or provide enough context for safe invocation. The agent lacks sufficient information to use this tool effectively in production scenarios.

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 but adds no parameter information. It doesn't explain what 'roomId' and 'newRoomId' represent, their format constraints, validation rules, or how they differ. The agent must rely solely on parameter names without semantic context, which is inadequate for a tool with 2 required parameters.

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 ('Update') and resource ('a Liveblocks room's ID'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'update-room' or 'update-room-subscription-settings' by specifying it updates the room ID specifically, not other room properties. However, it doesn't explicitly mention what 'room ID' refers to in the Liveblocks context.

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. It doesn't mention prerequisites (e.g., needing existing room access), consequences (e.g., whether old room ID becomes invalid), or when to choose this over other room-related tools like 'update-room' or 'create-room'. The agent must infer usage from the tool name alone.

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