Skip to main content
Glama
qq418716640

BotBell MCP Server

botbell_send

Send push notifications with interactive buttons to iPhone/Mac devices for alerts, reminders, and quick user responses.

Instructions

Send a push notification to the user's iPhone/Mac via BotBell. You can include action buttons for quick replies. Use type 'input' to let the user type a custom response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesMessage content (required, max 4096 chars)
titleNoMessage title (optional)
urlNoURL to attach (optional)
image_urlNoImage URL to attach (optional)
summaryNoCustom summary for long messages (optional, max 512 chars)
formatNoMessage format: 'text' (default) or 'markdown' for Markdown rendering
actions_descriptionNoDescription text shown above action buttons (optional, max 256 chars)
actionsNoQuick reply buttons (max 5). Use type 'input' for free-text option.
reply_modeNoControls how the recipient can reply: 'open' (default, free text + actions), 'actions_only' (only action buttons, no free text), 'none' (pure notification, no reply)

Implementation Reference

  • Handler for 'botbell_send' in PAT mode (using bot_id or alias).
    server.tool(
      "botbell_send",
      "Send a push notification to the user's iPhone/Mac via BotBell. " +
      (hasExtras
        ? "Use bot_id for your own bots or alias for external bots. Use botbell_list_bots to see all available targets. "
        : "Use botbell_list_bots first to find the bot_id. ") +
      "You can include action buttons for quick replies. Use type 'input' to let the user type a custom response.",
      sendSchema,
      async (args) => {
        try {
          const { bot_id, alias, ...msgArgs } = args as {
            bot_id?: string; alias?: string;
            message: string; title?: string; url?: string;
            image_url?: string; summary?: string; format?: string;
            actions_description?: string; actions?: unknown[];
            reply_mode?: string;
          };
          const body = buildMessageBody(msgArgs);
    
          // Route via alias (extra token)
          if (alias) {
            const btToken = resolveAlias(alias);
            if (!btToken) return errorResult(`Unknown alias "${alias}". Available: ${aliasNames.join(", ")}`);
            return await sendViaBotToken(btToken, apiBase, body);
          }
    
          // Route via bot_id (PAT)
          if (!bot_id) return errorResult("Provide either bot_id or alias.");
          const result = await api("POST", `/bots/${bot_id}/push`, body);
          if (!result.ok) return errorResult(`Failed to send: ${handleApiError(result)}`);
    
          const data = result.data.data as Record<string, unknown>;
          return textResult(
            `Notification sent successfully.\n` +
            `Message ID: ${data.message_id}\n` +
            `Delivered: ${data.delivered}\n` +
            `Timestamp: ${data.timestamp}`
          );
        } catch (error) {
          return errorResult(`Error: ${error instanceof Error ? error.message : String(error)}`);
        }
      }
    );
  • Handler for 'botbell_send' in Bot token mode (using default token or alias).
    server.tool(
      "botbell_send",
      "Send a push notification to the user's iPhone/Mac via BotBell. " +
      (hasExtras ? `You can also send via external bots: ${aliasNames.join(", ")}. ` : "") +
      "You can include action buttons for quick replies. Use type 'input' to let the user type a custom response.",
      sendSchema,
      async (args) => {
        try {
          const { alias, ...msgArgs } = args as {
            alias?: string;
            message: string; title?: string; url?: string;
            image_url?: string; summary?: string; format?: string;
            actions_description?: string; actions?: unknown[];
            reply_mode?: string;
          };
          const body = buildMessageBody(msgArgs);
    
          // Route via alias (extra token)
          if (alias) {
            const btToken = resolveAlias(alias);
            if (!btToken) return errorResult(`Unknown alias "${alias}". Available: ${aliasNames.join(", ")}`);
            return await sendViaBotToken(btToken, apiBase, body);
          }
    
          // Default: primary bot token
          return await sendViaBotToken(token, apiBase, body);
        } catch (error) {
          return errorResult(`Error: ${error instanceof Error ? error.message : String(error)}`);
        }
      }
    );
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 of behavioral disclosure. While it mentions the ability to include action buttons and use 'input' type, it lacks critical behavioral details such as whether this is a read-only or destructive operation, authentication requirements, rate limits, error conditions, or what happens after sending (e.g., confirmation, async response). For a notification-sending tool with zero annotation coverage, this is a significant gap.

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 concise with two sentences that directly address core functionality. It's front-loaded with the main purpose and includes practical guidance. However, the second sentence could be slightly more polished, and it doesn't waste words on redundant 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 the complexity of a notification-sending tool with 9 parameters, no annotations, and no output schema, the description is incomplete. It should cover more behavioral aspects (e.g., success/failure responses, side effects) and usage scenarios. The lack of output schema means the description should ideally hint at what to expect after invocation, which it doesn't.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 9 parameters thoroughly. The description adds minimal value beyond the schema by mentioning action buttons and the 'input' type, but it doesn't provide additional semantic context or usage examples for parameters like 'reply_mode' or 'format'. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Send a push notification to the user's iPhone/Mac via BotBell.' It specifies the action (send), resource (push notification), and target platform (iPhone/Mac via BotBell). It also distinguishes itself from its sibling botbell_get_replies by focusing on sending rather than retrieving notifications.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some usage guidance by mentioning 'You can include action buttons for quick replies' and 'Use type 'input' to let the user type a custom response,' which implies when to use certain features. However, it doesn't explicitly state when to use this tool versus alternatives or provide context about prerequisites or limitations.

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/qq418716640/botbell-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server