Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

List LINE Audiences

line_list_audiences
Read-onlyIdempotent

Retrieve audience groups from your LINE Official Account, filtered by status or name, to select audiences for broadcast messages.

Instructions

List audience groups on the OA. Audiences created via LINE OA Manager UI (e.g. chat-tag audiences, friend-path audiences, web-traffic audiences) also appear here — even though those types cannot be CREATED via Messaging API.

Status meanings:

  • READY: usable in narrowcast immediately

  • IN_PROGRESS: still indexing — wait ~10 minutes

  • FAILED: creation failed; recreate

  • EXPIRED: aged out; recreate

Args:

  • status_filter: 'all' (default) | 'READY' | 'IN_PROGRESS' | 'FAILED' | 'EXPIRED'.

  • name_contains: optional substring filter (case-insensitive).

  • limit, page: pagination (default 20/page).

  • oa: optional OA id.

Returns: { total: number, count: number, page: number, audiences: [{ audience_group_id, name, status, audience_count?, created, type? }], has_more: boolean }

Examples:

  • "ดู audience ที่พร้อมส่ง" → { status_filter: "READY" }

  • "หา audience ชื่อ vip" → { name_contains: "vip" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
status_filterNoFilter audiences by readiness status. Default 'all'.all
name_containsNoOptional substring filter on audience name (case-insensitive).
limitNoPage size (max 100).
pageNoPage number (1-indexed).
oaNo
response_formatNomarkdown
Behavior5/5

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

Annotations indicate readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds value by explaining that audiences from UI appear here but cannot be created via API, and details return format and status behavior beyond annotations.

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 for status meanings, args, returns, and examples. Front-loaded purpose, no unnecessary sentences.

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?

Despite no output schema, description includes a complete return structure. Covers status meanings, filtering, pagination, and examples, making it fully actionable.

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

Parameters5/5

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

Schema covers 67% of parameters; description explains status_filter enum values, name_contains substring, and pagination. Provides examples that clarify usage, adding meaning beyond schema.

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 'List audience groups on the OA' and explicitly notes that audiences created via UI also appear but cannot be created via API, differentiating it from tools like line_delete_audience or 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 Guidelines4/5

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

Provides detailed status meanings with actionable advice (e.g., wait for IN_PROGRESS, recreate for FAILED) and examples of queries. Does not explicitly exclude alternatives but context is sufficient.

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