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 retargeting audience from users who clicked or opened a previous broadcast. Use the source request ID to create the audience group, enabling re-engagement without 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?

Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), the description adds that the source message must be ≥24h old, minimum 50 users, region-gated to JP/TW/TH, and returns an object with audience_group_id. No contradiction.

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?

Well-structured with sections: Args, Returns, Notes, Example workflow. Every sentence is informative, no fluff. Front-loaded with purpose.

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?

No output schema, but return values documented. Notes cover constraints and prerequisites. Example workflow shows integration with line_send_message. Complete for a 5-param tool with no output schema.

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 60%. The description explains all parameters in Args section, adding context like source_request_id from previous call, type='clicks'/'opens', click_url optional. Adds value beyond schema for name and oa which lack 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 clearly states it creates a LINE audience from people who clicked or opened a previous broadcast/narrowcast. It uses specific verbs ('create', 'retarget') and resources ('LINE audience', 'engagement'), and distinguishes from sibling tool line_build_audience_from_csv.

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 says when to use ('retarget without a CRM'), provides an example workflow, and notes prerequisites (source message ≥24h old, minimum 50 users). Does not state when not to use, but context is clear.

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