Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Build retargeting audience from prior engagement

line_build_audience_from_engagement

Build a LINE audience from users who clicked or opened a previous broadcast or narrowcast. Use the source message request ID to retarget engaged users without needing a CRM.

Instructions

Create a LINE audience from people who clicked or opened a previous broadcast / narrowcast. The killer "retarget without a CRM" tool.

Args:

  • name: New audience name.

  • source_request_id: request_id from a previous line_send_message call (saved in its return value).

  • type: 'clicks' (default) or 'opens'.

  • click_url: optional — limit to a specific clicked URL (for 'clicks' only).

  • oa: optional OA id.

Returns: { audience_group_id, name, type }

Notes:

  • LINE requires the source message to be ≥24 hours old before the engagement audience is reliable.

  • Minimum ~50 users for the audience to be usable in narrowcast.

  • Region-gated to JP / TW / TH (+ premium).

Example workflow:

  1. line_send_message(..., target: narrowcast) → save request_id

  2. Wait 24h

  3. line_build_audience_from_engagement({ source_request_id, type: 'clicks' })

  4. line_send_message(..., target: { audience: 'new-engagement-audience' })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
source_request_idYesThe request_id returned by a prior line_send_message (narrowcast/multicast/push/broadcast).
typeNo'clicks' = audience of users who clicked any link in the source message; 'opens' = users who saw it.clicks
click_urlNoIf 'clicks' and you only want users who clicked a specific URL, set it here.
oaNo
Behavior5/5

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

Annotations show readOnlyHint=false and openWorldHint=true; the description adds critical behavioral details: source message must be >=24h old, minimum ~50 users, region-gated to JP/TW/TH. No contradiction with annotations.

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

Conciseness4/5

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

The description is well-structured (purpose sentence, Args list, Notes, Example workflow) and front-loaded. A few words could be trimmed, but it's organized and each part earns its place.

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?

Provides full usage context: prerequisites (24h wait, min users), region limits, and return format. No output schema, but the explanation of return values (audience_group_id, name, type) suffices for a 5-param creation tool.

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 has 60% coverage (3/5 params described); the description’s Args section covers all 5 params with narrative context (e.g., source_request_id comes from prior call, click_url optional). Adds value beyond schema but some redundancy.

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 clearly states it creates an audience from prior engagement (clicks/opens), using a specific verb and resource. It distinguishes from siblings like line_build_audience_from_csv (different source) and line_list_audiences (read-only).

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?

The description provides explicit when-to-use context (retargeting without CRM) and a full example workflow, including a prerequisite (wait 24h). It implicitly excludes other audience-building methods.

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