Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Send LINE Message (universal)

line_send_message

Send text, templates, flex, stickers, coupons, images, or videos to any target—individual, audience, or everyone—while auto-selecting the LINE API and enforcing validation and quota safeguards.

Instructions

Universal LINE sender. Auto-picks the API (reply/push/multicast/narrowcast/broadcast) from the target shape; message shape selects text/template/flex/sticker/coupon/image/video. Feed pre-built objects from line_design_imagemap/line_design_card/line_design_flex via message.message_json; native coupons from line_manage_coupon via message.coupon_id; images hosted by line_prepare_image via message.image.prepared_key (no URLs needed).

mode: send_now (default) sends immediately; draft returns a LINE OA Manager handoff package (URL + Flex JSON + steps) — use when the user wants to SCHEDULE, since the Messaging API can't schedule but the OA Manager UI can; dry_run validates + estimates cost without sending.

Safety: pre-flight /validate before spending quota; Quota Guardian blocks if projected cost >95% of remaining quota unless confirm=true; broadcast { everyone:true } requires confirm=true; quiet-hours 22:00–08:00 BKK warns unless force=true; quiet_push silences the recipient device; reply tokens expire ~1 min (falls back to a push hint).

Returns send_now → { success, transport, request_id?, recipient_count_estimated, quota, warnings[] }; draft and dry_run return their own shapes. Narrowcast needs ~24h before line_get_message_stats shows engagement.

Example: "ส่งโปรให้ผู้หญิง 25-44 กรุงเทพ" → target.filter { genders:["female"], ages:["age_25","age_30"], areas:["bangkok"] }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
oaNoOA id (multi-OA). Omit to use active OA.
modeNosend_now (default) sends immediately; draft returns a handoff package for LINE OA Manager UI; dry_run validates + estimates without sending.send_now
forceNoOverride quiet-hours warning (22:00–08:00 BKK). Defaults false; LINE Thai customers prefer not to be pinged at night.
targetYesWho to send to. Pick one shape: { reply_to } | { user_id } | { user_ids[] } | { audience } | { filter } | { everyone: true }
confirmNoRequired to be true when projected cost > 95% of remaining quota, or when target.everyone === true.
messageYesWhat to send. Pick one shape: { text } | { template, data } | { flex_json, alt_text } | { sticker } | { coupon_id } | { image: { original_content_url, preview_image_url } or { prepared_key } } | { video: {...} } | { message_json } (pre-built object from the design tools)
quiet_pushNoSuppress push notification on recipient device (silent send). Default false.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations are minimal (readOnlyHint=false, openWorldHint=true), so the description carries the burden and delivers: auto-pick behavior, reply token expiry, quiet-hours warnings, Quota Guardian blocking, and per-mode return shapes. This far exceeds annotation-only knowledge and sets accurate expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Though long, the description is well-structured with clear sections: purpose, modes, safety, returns, and an example. Every sentence adds critical operational detail, and the key purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even without an output schema, the description explicitly outlines the return shape for send_now and mentions draft/dry_run shapes. It covers prerequisites, safety, error-avoidance behaviors, and downstream stats timing, making it thoroughly complete for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description enriches parameter semantics by explaining the mapping from target shapes to API types and from message shapes to content types. It also ties confirm, force, quiet_push, and mode to real-world behaviors, adding value beyond schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Universal LINE sender' and immediately explains the auto-pick logic for API and message type, which is specific and clear. It also differentiates from siblings by referencing line_design_*, line_manage_coupon, and line_prepare_image as inputs for this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use draft (for scheduling, because Messaging API can't schedule) versus send_now and dry_run. Includes safety guidance about quota, quiet-hours, and broadcast confirmation, plus references line_get_message_stats for narrowcast follow-up.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wasintoh/line-oa-mcp-ultimate'

If you have feedback or need assistance with the MCP directory API, please join our Discord server