line-bot-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DESTINATION_USER_ID | No | Default user ID to receive messages when no userId is provided to tools. | |
| CHANNEL_ACCESS_TOKEN | Yes | Channel Access Token for LINE Messaging API |
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. |
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
Tools are mostly distinct by action and resource (push vs broadcast, text vs flex, rich menu CRUD). However, push_text_message and broadcast_text_message differ only by audience, and the same for flex messages, which could cause confusion if descriptions aren't read carefully.
Most tools follow a consistent verb_noun pattern (get_, push_, broadcast_, create_, delete_, set_, cancel_). Minor inconsistency: get_follower_ids uses 'follower' while other tools use 'user' or 'rich_menu', and set_rich_menu_default/cancel_rich_menu_default are slightly verbose but still clear.
12 tools is a reasonable size for a LINE bot server covering messaging, rich menus, and user data. The count is slightly high but each tool serves a distinct function within the domain.
The server covers core messaging (push/broadcast), rich menu management (create, delete, default), and user info (profile, follower IDs, quota). Missing obvious operations like updating a rich menu, sending image/video/sticker messages, or replying to webhook events, which are common LINE bot workflows.