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 userId, DESTINATION_USER_ID is required. | |
| CHANNEL_ACCESS_TOKEN | Yes | Channel Access Token. You can confirm this by following the instructions in the README. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| push_text_messageA | 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_profileA | 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_listA | Get the list of rich menus associated with your LINE Official Account. |
| delete_rich_menuB | Delete a rich menu from your LINE Official Account. |
| set_rich_menu_defaultB | Set a rich menu as the default rich menu. |
| cancel_rich_menu_defaultB | Cancel the default rich menu. |
| create_rich_menuB | Create a rich menu based on the given actions. Generate and upload a rich menu image based on the given action. This rich menu will be registered as the default. |
| get_follower_idsA | Get a list of user IDs of users who have added the LINE Official Account as a friend. This allows you to obtain user IDs for sending messages without manually preparing them. |
| get_group_summaryB | Get the group chat summary including group ID, group name, and group icon URL, using the group ID. |
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 13 tools
Push vs broadcast tools are clearly differentiated by description (single user vs all followers), and text vs flex variants are distinct. The 2x2 grid of push/broadcast × text/flex and the cluster of rich-menu operations are well-bounded, though an agent must read carefully to pick correctly.
Every tool follows a consistent snake_case verb-first pattern (get_, create_, delete_, set_, cancel_, push_, broadcast_). The convention is predictable throughout with no mixed styles.
13 tools is well within the ideal range and each tool earns its place, covering messaging, rich-menu management, and account/user lookups without redundancy.
Core lifecycle is covered: messaging (push/broadcast), rich-menu CRUD plus default set/cancel, profile, quota, followers, and group summary. Gaps remain (no per-user rich-menu linking, no multicast/narrowcast, no get-single-rich-menu), but agents can work around these.