Skip to main content
Glama
liveblocks

Liveblocks

Official
by liveblocks

get-notification-settings

Retrieve user notification preferences for Liveblocks collaboration tools to manage alerts and communication settings.

Instructions

Get a Liveblocks notification settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYes

Implementation Reference

  • The handler function that executes the get-notification-settings tool by calling the Liveblocks API to retrieve notification settings for the given userId.
    async ({ userId }, extra) => {
      return await callLiveblocksApi(
        getLiveblocks().getNotificationSettings(
          { userId },
          { signal: extra.signal }
        )
      );
    }
  • Input schema for the get-notification-settings tool, requiring a userId string.
    {
      userId: z.string(),
    },
  • src/server.ts:758-772 (registration)
    Registration of the get-notification-settings tool using McpServer.tool method.
    server.tool(
      "get-notification-settings",
      "Get a Liveblocks notification settings",
      {
        userId: z.string(),
      },
      async ({ userId }, extra) => {
        return await callLiveblocksApi(
          getLiveblocks().getNotificationSettings(
            { userId },
            { 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 the full burden. It states 'Get' implying a read operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error conditions, or what the return format might be (e.g., JSON structure). This is a significant gap for a tool with no annotation coverage.

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

Conciseness4/5

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

The description is a single, straightforward sentence with no wasted words, making it appropriately concise. However, it lacks front-loading of critical details like parameter context or usage distinctions, which slightly reduces its effectiveness.

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 tool's complexity (a read operation with 1 parameter), no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain what 'notification settings' includes, how to interpret results, or address potential errors, leaving significant gaps for an AI agent to use it correctly.

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?

The input schema has 1 parameter (userId) with 0% description coverage, meaning the schema provides no semantic context. The description adds no information about the parameter, such as what 'userId' represents (e.g., a user identifier string) or how to obtain it. It fails to compensate for the low schema coverage.

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

Purpose3/5

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

The description states the action ('Get') and resource ('Liveblocks notification settings'), providing a basic purpose. However, it's vague about what 'notification settings' specifically entails and doesn't distinguish from siblings like 'get-user-room-subscription-settings' or 'get-room-subscription-settings', which might involve similar settings retrieval.

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-inbox-notification' or 'get-room-subscription-settings' that might retrieve related data, the description lacks context on usage scenarios, prerequisites, or exclusions.

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