Skip to main content
Glama
liveblocks

Liveblocks

Official
by liveblocks

delete-room-subscription-settings

Remove subscription settings from a Liveblocks room to manage user notifications and access permissions.

Instructions

Delete a Liveblocks room's subscription settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomIdYes
userIdYes

Implementation Reference

  • src/server.ts:623-638 (registration)
    Registration of the MCP tool 'delete-room-subscription-settings', including inline Zod schema for input parameters (roomId, userId) and the handler function that invokes the Liveblocks API via getLiveblocks().deleteRoomSubscriptionSettings wrapped in callLiveblocksApi.
    server.tool(
      "delete-room-subscription-settings",
      `Delete a Liveblocks room's subscription settings`,
      {
        roomId: z.string(),
        userId: z.string(),
      },
      async ({ roomId, userId }, extra) => {
        return await callLiveblocksApi(
          getLiveblocks().deleteRoomSubscriptionSettings(
            { roomId, userId },
            { signal: extra.signal }
          )
        );
      }
    );
  • Zod schema defining input parameters for the tool: roomId and userId as strings.
    {
      roomId: z.string(),
      userId: z.string(),
    },
  • Handler function for the tool that calls the Liveblocks client to delete room subscription settings for a user, passing roomId and userId, with abort signal support.
    async ({ roomId, userId }, extra) => {
      return await callLiveblocksApi(
        getLiveblocks().deleteRoomSubscriptionSettings(
          { roomId, userId },
          { signal: extra.signal }
        )
      );
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't specify whether this operation is reversible, what permissions are required, what happens to associated data, or what the response looks like. For a destructive operation with zero annotation coverage, this represents a significant gap in behavioral 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 that gets straight to the point with zero wasted words. It's appropriately sized for a tool with a clear primary function and represents excellent conciseness.

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?

For a destructive mutation tool with no annotations, no output schema, and 0% parameter documentation coverage, the description is inadequate. It doesn't explain what happens after deletion, whether the operation is idempotent, what error conditions might occur, or provide any context about the subscription settings being deleted.

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?

With 0% schema description coverage for both parameters (roomId and userId), the description provides no information about what these parameters mean or how they should be used. The description doesn't mention either parameter, leaving the agent with no semantic understanding 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 ('Delete') and the resource ('a Liveblocks room's subscription settings'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from similar sibling tools like 'delete-room' or 'delete-notification-settings', which would require explicit differentiation to earn a 5.

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 sibling tools like 'delete-room', 'delete-notification-settings', and 'update-room-subscription-settings' available, there's no indication of when this specific deletion operation is appropriate versus those other options.

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