Skip to main content
Glama
acquo

LINE Bot MCP Server (SSE Support)

by acquo
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

broadcast_flex_message

Send customizable flex messages to all LINE Official Account users using bubble or carousel layouts for rich content delivery.

Instructions

Broadcast a highly customizable flex message via LINE to all users who have added your LINE Official Account. Supports both bubble (single container) and carousel (multiple swipeable bubbles) layouts. Please be aware that this message will be sent to all users.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYes

Implementation Reference

  • src/tools/broadcastFlexMessage.ts:27-38 (handler)
    The implementation of the broadcast_flex_message handler, which uses the LINE MessagingApiClient to broadcast the message.
    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/broadcastFlexMessage.ts:18-40 (registration)
    The registration method for the broadcast_flex_message tool using the McpServer.
    register(server: McpServer) {
  server.tool(
    "broadcast_flex_message",
    "Broadcast a highly customizable flex message via LINE to all users who have added your LINE Official Account. " +
      "Supports both bubble (single container) and carousel (multiple swipeable bubbles) layouts. Please be aware that " +
      "this message will be sent to all users.",
    {
      message: flexMessageSchema,
    },
    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.5/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. While it mentions the broadcast scope and layout options, it lacks critical information about permissions required, rate limits, whether this is a paid service, delivery guarantees, or what happens if the message fails. For a broadcast tool with significant impact, this is insufficient.

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 perfectly concise with two sentences that each earn their place. The first sentence covers purpose and capabilities, the second provides critical behavioral warning about broadcast scope. No wasted words, well-structured.

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 broadcast tool with no annotations, no output schema, and complex nested parameters, the description is incomplete. It covers the 'what' but misses critical 'how' details about parameter construction, authentication requirements, error handling, and response format. The warning about broadcast scope is valuable but insufficient for full contextual understanding.

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 and 1 complex nested parameter, the description provides minimal parameter guidance. It mentions bubble and carousel layouts but doesn't explain the 'message' object structure, 'altText' purpose, or how to construct the 'contents' property. The description doesn't compensate for the schema's lack of documentation.

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'), the resource ('flex message via LINE'), and the target audience ('all users who have added your LINE Official Account'). It distinguishes from sibling tools like push_flex_message by specifying this is a broadcast to all users rather than a targeted push.

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 about when to use this tool (sending to all users) and implicitly distinguishes it from push_flex_message (which likely sends to specific users). However, it doesn't explicitly state when NOT to use it or mention alternatives like broadcast_text_message for simpler messages.

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