LINE

@LINE show me the rich menu definition for menu ID richmenu-abc123 and tell me what each tap area does

Retrieved rich menu 'Main Navigation' (1200×810px). It has 4 tap areas: top-left opens the product catalog webview, top-right triggers a 'View Cart' postback, bottom-left sends the text 'Talk to support', and bottom-right opens the store locator URI. The menu uses a light blue background with icon labels. This illustrative example shows how the MCP returns the full canvas layout and action bindings for inspection.

Useful for auditing which actions fire when users tap your menu. Requires the rich menu ID from your LINE Official Account Manager or a prior create call. The MCP returns the definition only—it won't show you the uploaded image file or tell you if the menu is currently set as default.

@LINE create a new rich menu with two buttons: one that opens our FAQ page and one that sends the message 'Request callback', then upload the menu image from our design folder

Created rich menu 'Customer Support v2' (ID: richmenu-xyz789) with a 2-area layout. Left area (50% width) opens https://example.com/faq in the in-app browser; right area sends 'Request callback' as a user message. Uploaded menu-design-final.png (1200×810px JPEG). The menu is now stored but not yet visible to users—you must set it as the default rich menu or link it to specific user IDs to display it.

Demonstrates end-to-end menu creation and image upload in one workflow. If the image upload fails (wrong dimensions, file too large), the MCP automatically deletes the newly created menu definition to avoid orphaned entries. You still need a separate call to make the menu live for your audience.

@LINE get the delivery count for all broadcast messages sent on 2025-01-15 and compare it to the previous week's daily average

On 2025-01-15 (UTC+9), you sent 8,420 broadcast messages. The prior 7 days averaged 6,150 messages/day, so yesterday was 37% above your weekly baseline. Note: LINE returns delivery counts 2–3 days after the target date; if you query too early, the result will be 'unready'. This example assumes the data is available and illustrates how the MCP pairs raw counts with AI-driven percentage analysis.

Helpful for tracking campaign reach and spotting send-volume trends. LINE enforces a UTC+9 calendar-date boundary and may return 'unavailable_for_privacy' if your account type restricts analytics. The MCP can only retrieve counts for dates at least 48 hours in the past—real-time delivery stats are not supported.

When LINE rich menus beat a chatbot for local support

A 6-person home-services company in Japan uses LINE as its primary customer channel because 90% of their clients already have the app. They built a rich menu with tappable buttons for booking, FAQs, and emergency contact instead of training a conversational bot. The Create Rich Menu with Image tool lets them deploy a new menu layout in one call, and Link or Unlink User Rich Menu personalizes the experience for repeat customers versus first-timers. This works because their support volume is under 200 conversations a week and queries fall into five predictable buckets. If your team fields more than 500 varied questions monthly or operates outside Japan, LINE's closed ecosystem becomes a liability. For small local businesses with a LINE-native customer base, this MCP turns the app into a zero-training support hub.

LINE broadcast messaging for hyperlocal event promotion

A 3-person nonprofit running monthly meetups in Osaka uses LINE Official Account to announce events because email open rates dropped below 12%. They send a broadcast message with an embedded registration link, then use Get Message Delivery Count to track send success and adjust timing for the next campaign. The MCP's push and multicast tools let them segment by past attendance without leaving Switchy, and Download Message Content Preview pulls user-submitted event photos for the next announcement. This scales to about 2,000 subscribers before LINE's rate limits and per-message costs make email automation cheaper. If your community is under 3,000 people and concentrated in Japan or Taiwan, LINE's 85% open rates justify the API_KEY setup. Beyond that threshold, switch to a multichannel tool with better analytics.

Per-user rich menus for tiered loyalty without custom dev

A 4-location ramen franchise uses LINE to run a points program because their average customer is 28 and checks LINE 40 times a day. They created three rich menu templates—bronze, silver, gold—and use Link or Unlink User Rich Menu to swap a customer's menu when they hit a new tier. The List Chat Member IDs tool pulls group-chat participants for a VIP tasting event, and Get Rich Menu confirms the current layout before pushing an update. This works because their customer base is under 8,000 and menu changes happen weekly, not hourly. If you're managing more than 15,000 users or need real-time menu personalization, LINE's API rate limits will bottleneck you. For small franchises with a mobile-first, Japan-based audience, this MCP turns loyalty into a visual, zero-app-download experience.