Skip to main content
Glama
acquo

LINE Bot MCP Server (SSE Support)

by acquo

push_text_message

Send plain text messages to LINE users through the LINE Bot MCP Server. This tool enables AI agents to communicate with users via text without formatting.

Instructions

Push a simple text message to a user via LINE. Use this for sending plain text messages without formatting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdNoThe user ID to receive a message. Defaults to DESTINATION_USER_ID.
messageYes

Implementation Reference

  • The tool execution handler that calls the messaging API.
    async ({ userId, message }) => {
      if (!userId) {
        return createErrorResponse(NO_USER_ID_ERROR);
      }
    
      try {
        const response = await this.client.pushMessage({
          to: userId,
          messages: [message as unknown as messagingApi.Message],
        });
        return createSuccessResponse(response);
      } catch (error) {
        return createErrorResponse(
          `Failed to push message: ${error.message}`,
        );
      }
    },
  • Tool registration using server.tool.
    server.tool(
      "push_text_message",
      "Push a simple text message to a user via LINE. Use this for sending plain text messages without formatting.",
      {
        userId: userIdSchema,
        message: textMessageSchema,
      },
      async ({ userId, message }) => {
        if (!userId) {
          return createErrorResponse(NO_USER_ID_ERROR);
        }
    
        try {
          const response = await this.client.pushMessage({
            to: userId,
            messages: [message as unknown as messagingApi.Message],
          });
          return createSuccessResponse(response);
        } catch (error) {
          return createErrorResponse(
            `Failed to push message: ${error.message}`,
          );
        }
      },
    );
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. It mentions the message type constraint ('plain text') but doesn't cover critical aspects like authentication requirements, rate limits, error conditions, or what happens after sending (e.g., delivery confirmation). For a messaging tool with zero annotation coverage, this leaves significant gaps.

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 efficiently structured in two sentences: the first states the core functionality, the second provides usage guidance. Every word earns its place with zero redundancy or fluff, making it easy to parse quickly.

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 messaging tool with no annotations, no output schema, and incomplete parameter documentation (50% coverage), the description is insufficient. It doesn't address authentication, response format, error handling, or platform-specific constraints that an agent would need to use this tool effectively in context with its siblings.

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 50% (only 'text' parameter has description). The description adds no parameter-specific information beyond what's implied by the tool's purpose. It doesn't explain 'userId' usage or the nested 'message' object structure, so it doesn't compensate for the schema coverage gap, resulting in a baseline score.

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 ('Push'), resource ('text message'), target ('to a user via LINE'), and scope ('plain text messages without formatting'). It distinguishes from formatting-rich alternatives but doesn't explicitly name sibling tools like 'push_flex_message' for full differentiation.

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 implies when to use it ('for sending plain text messages without formatting'), suggesting alternatives exist for formatted messages. However, it doesn't explicitly state when NOT to use it or name specific alternatives like 'push_flex_message', leaving some ambiguity about usage context.

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