LINE Bot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DESTINATION_USER_ID | No | The default user ID of the recipient. If the Tool's input does not include user_id, DESTINATION_USER_ID is required | |
| CHANNEL_ACCESS_TOKEN | Yes | Channel Access Token for LINE Official Account |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| push_text_messageB | Push a simple text message to a user via LINE. Use this for sending plain text messages without formatting. |
| push_flex_messageB | Push a highly customizable flex message to a user via LINE. Supports both bubble (single container) and carousel (multiple swipeable bubbles) layouts. |
| broadcast_text_messageA | 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. |
| broadcast_flex_messageA | 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. |
| get_profileB | Get detailed profile information of a LINE user including display name, profile picture URL, status message and language. |
| get_message_quotaA | Get the message quota and consumption of the LINE Official Account. This shows the monthly message limit and current usage. |
| get_rich_menu_listB | Get the list of rich menus associated with your LINE Official Account. |
| delete_rich_menuC | Delete a rich menu from your LINE Official Account. |
| set_rich_menu_defaultC | Set a rich menu as the default rich menu. |
| cancel_rich_menu_defaultB | Cancel the default rich menu. |
| push_gemini_textC | Generate text with Gemini and push it to a LINE user as a text message. |
| push_gemini_flexA | Generate a LINE Flex message (bubble/carousel) from a natural language prompt using Gemini, then push it to a user. |
| gemini_commandB | Use Gemini to plan and execute one LINE action (get profile, get rich menu list, get message quota, push/broadcast text or flex). |
| push_messagesC | Push one or more LINE messages to a user (generic). |
| broadcast_messagesC | Broadcast one or more LINE messages to all followers (generic). |
| query_mssqlA | Run a read-only MSSQL query (SELECT/WITH). Returns columns, rowCount, and sliced rows for preview. |
| export_mssql_knowledgeA | Export MSSQL schema (tables/columns) into a Markdown knowledge file for Q/A. |
| ai_query_mssqlA | Generate a safe read-only MSSQL SELECT from instruction via Gemini, validate, execute, and return rows. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
There is significant overlap between broadcast/push variants (e.g., broadcast_text_message vs broadcast_messages vs broadcast_flex_message) and between Gemini-integrated tools (gemini_command vs push_gemini_flex vs push_gemini_text vs ai_query_mssql), which could lead to confusion about which tool to use for similar tasks. However, the descriptions help clarify some distinctions, such as between generic and specific message types.
Most tools follow a consistent snake_case verb_noun pattern (e.g., broadcast_text_message, get_profile, delete_rich_menu), with clear actions like broadcast, push, get, set, delete, query, and export. Minor deviations include ai_query_mssql (starts with 'ai_') and gemini_command (uses 'command' instead of a more specific verb), but overall the naming is predictable and readable.
With 18 tools, the count feels borderline heavy for a LINE bot server, as it includes many overlapping or specialized variants (e.g., multiple broadcast and push tools). While the scope covers messaging, user management, rich menus, and database queries, the set could be streamlined without losing functionality, making it slightly overwhelming for an agent to navigate.
The tool surface provides good coverage for LINE bot operations, including messaging (broadcast/push with text/flex), user profile retrieval, rich menu management (list/set/cancel/delete), and database queries (MSSQL with AI integration). Minor gaps include lack of tools for updating user data or handling webhook events, but core workflows are well-supported, allowing agents to perform essential tasks without major dead ends.