Skip to main content
Glama
acquo

LINE Bot MCP Server (SSE Support)

by acquo
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

broadcast_text_message

Send plain text messages to all followers of a LINE Official Account for announcements, updates, or general communication.

Instructions

Broadcast a simple text message via LINE to all users who have followed your LINE Official Account. Use this for sending plain text messages without formatting. Please be aware that this message will be sent to all users.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYes

Implementation Reference

  • src/tools/broadcastTextMessage.ts:26-37 (handler)
    The async handler that executes the broadcast message operation using the MessagingApiClient.
    async ({ message }) => {
  try {
    const response = await this.client.broadcast({
      messages: [message as unknown as messagingApi.Message],
    });
    return createSuccessResponse(response);
  } catch (error) {
    return createErrorResponse(
      `Failed to broadcast message: ${error.message}`,
    );
  }
},
  • src/tools/broadcastTextMessage.ts:18-38 (registration)
    Registration of the broadcast_text_message tool within the MCP server.
    register(server: McpServer) {
  server.tool(
    "broadcast_text_message",
    "Broadcast a simple text message via LINE to all users who have followed your LINE Official Account. Use this for sending " +
      "plain text messages without formatting. Please be aware that this message will be sent to all users.",
    {
      message: textMessageSchema,
    },
    async ({ message }) => {
      try {
        const response = await this.client.broadcast({
          messages: [message as unknown as messagingApi.Message],
        });
        return createSuccessResponse(response);
      } catch (error) {
        return createErrorResponse(
          `Failed to broadcast message: ${error.message}`,
        );
      }
    },
  );

Tool Definition Quality

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the broadcast nature ('sent to all users') and plain text constraint, but lacks details on permissions, rate limits, error handling, or response format. It adequately describes the core behavior but misses operational context.

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 front-loaded with the core purpose, uses two efficient sentences with zero waste, and avoids redundancy. Every phrase adds value (e.g., 'without formatting', 'to all users').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 0% schema coverage, the description is incomplete. It covers the what and who but lacks how (e.g., success/failure responses), why (use cases), and operational constraints. It's minimally viable but has clear gaps for a broadcast tool.

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 0%, so the description must compensate. It implies a 'message' parameter but does not explain its structure or the 'text' field's semantics beyond 'plain text content'. The description adds minimal value beyond the schema's technical constraints.

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 specific action ('Broadcast a simple text message'), the target resource ('via LINE to all users who have followed your LINE Official Account'), and distinguishes it from siblings by specifying 'plain text messages without formatting' (unlike broadcast_flex_message or push_flex_message).

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('for sending plain text messages without formatting'), but does not explicitly mention when not to use it or name specific alternatives (e.g., push_text_message for targeted messages). It implies a broadcast context but lacks explicit 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/acquo/line-bot-mcp-server-sse'

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