LINE MCP integration for AI agents.
Connect AI agents to LINE through 5 structured actions, including get bot info, send broadcast text, and get profile. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the LINE integration exposes
The LINE Agent App exposes 5 provider-backed actions for communication and social work. Its current contract lets an authorized agent get profile and chat settings for the connected line official account, send up to five text messages to all friends of the line official account, and get the line profile of a user who can interact with the connected bot. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected LINE account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real LINE capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_bot_infoREADGet profile and chat settings for the connected LINE Official Account.
send_broadcast_textWRITESend up to five text messages to all friends of the LINE Official Account.
INPUTS: texts / notificationDisabled / retryKey
get_profileREADGet the LINE profile of a user who can interact with the connected bot.
INPUTS: userId
send_multicast_textWRITESend up to five text messages to as many as 500 LINE users.
INPUTS: to / texts / notificationDisabled / retryKey
send_push_textWRITESend up to five text messages to one LINE user, group, or multi-person chat.
INPUTS: to / texts / notificationDisabled / retryKey
INPUT CONTRACTS
Know what the action needs before it runs.
send_broadcast_text
textsREQUIRED- The text messages to send in order.
notificationDisabledOPTIONAL- Whether LINE should suppress push notifications for the sent messages.
retryKeyOPTIONAL- An optional caller-generated UUID used by LINE to deduplicate a retried request.
get_profile
userIdREQUIRED- The LINE user ID obtained from a Messaging API webhook.
send_multicast_text
toREQUIRED- The target LINE user IDs.
textsREQUIRED- The text messages to send in order.
notificationDisabledOPTIONAL- Whether LINE should suppress push notifications for the sent messages.
retryKeyOPTIONAL- An optional caller-generated UUID used by LINE to deduplicate a retried request.
send_push_text
toREQUIRED- The target LINE user, group, or room ID.
textsREQUIRED- The text messages to send in order.
notificationDisabledOPTIONAL- Whether LINE should suppress push notifications for the sent messages.
retryKeyOPTIONAL- An optional caller-generated UUID used by LINE to deduplicate a retried request.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Bot Info
Get profile and chat settings for the connected LINE Official Account. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_bot_infoControl Send Broadcast Text
Send up to five text messages to all friends of the LINE Official Account. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
send_broadcast_textVerify with Get Profile
Get the LINE profile of a user who can interact with the connected bot. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_profileSAFETY BOUNDARY
Operate LINE with explicit limits
- Authorize LINE with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in LINE rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the LINE task completed successfully.
CONNECTION MODEL
API key
LINE Messaging API channel access token sent as a Bearer credential. Manage it at https://developers.line.biz/console/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by LINE.