LINE Bot MCP Server
OfficialServer 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. You can confirm this by following the instructions at https://developers.line.biz/en/docs/messaging-api/getting-user-ids/#get-own-user-id | |
| CHANNEL_ACCESS_TOKEN | Yes | Channel Access Token. You can confirm this by following the instructions at https://developers.line.biz/en/docs/basics/channel-access-token/#long-lived-channel-access-token |
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_messageC | 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_menuA | 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. |
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 12 tools
Each tool targets a distinct action and resource: broadcast vs push, text vs flex, rich menu management (create, delete, set, cancel, list), and informational (get follower IDs, quota, profile). No two tools have overlapping purposes.
All tools follow a consistent verb_noun pattern using snake_case (e.g., broadcast_flex_message, create_rich_menu, get_profile). No mixing of conventions.
With 12 tools, the server is well-scoped, covering essential LINE Bot operations without unnecessary bloat. The count falls comfortably within the ideal 3-15 range.
The tool set covers core messaging (broadcast/push, text/flex), rich menu lifecycle (create, delete, list, default), and user/account info (followers, profile, quota). Minor gaps like replying to messages or sending media types are absent, but the server is sufficiently functional for its intended use.