Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Update LINE Audience

line_update_audience

Append user IDs to an existing LINE upload audience or rename the audience group.

Instructions

Mutate an existing LINE audience group (upload type). Two modes.

Only Messaging-API-created (upload) audiences accept add_users. Audiences built in LINE OA Manager UI (chat-tag, friend-path, web-traffic) are read-only here and LINE will reject mutation.

Args:

  • mode ('add_users' | 'rename'): what to change.

  • audience_group_id (number): target audience id (from line_list_audiences).

  • user_ids (string[], add_users only): LINE user IDs to append.

  • description (string, rename only): the new audience name.

  • oa (string, optional): OA id. Default = active OA.

Returns:

  • add_users → { mode, audience_group_id, added_count }

  • rename → { mode, audience_group_id, new_description }

Examples:

  • "เพิ่ม 3 คนเข้า audience 12345" → { mode: "add_users", audience_group_id: 12345, user_ids: ["U1...", "U2...", "U3..."] }

  • "เปลี่ยนชื่อ audience 12345 เป็น VIP มิ.ย." → { mode: "rename", audience_group_id: 12345, description: "VIP มิ.ย." }

Errors:

  • Missing user_ids for add_users / missing description for rename → inline input error.

  • LINE rejects mutation on non-upload audiences (e.g. chat-tag) → LineApiError surfaced.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesadd_users: append user IDs to an existing upload audience; rename: change an audience's display name.
audience_group_idYesTarget audience group id (from line_list_audiences).
user_idsNoRequired for mode='add_users'. LINE user IDs to append.
descriptionNoRequired for mode='rename'. The new audience name (≤120 chars).
oaNoOptional OA id; defaults to active OA.
Behavior5/5

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

Annotations indicate mutation (readOnlyHint=false). Description adds that only upload-type audiences accept add_users, that rename changes the display name, and that errors like LineApiError may occur. 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.

Conciseness5/5

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

Well-structured with a summary, bullet points for args/returns/examples/errors. Each sentence is informative and concise without redundancy.

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, the description includes return types for each mode and error handling. Covers all necessary behavioral and usage details for a tool with conditional logic.

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 covers all parameters (100% coverage). Description adds value with examples showing conditional requirements and usage context, but the schema already provides detailed 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 mutates an existing LINE audience group (upload type) with two modes (add_users, rename). It distinguishes from sibling tools like line_delete_audience and line_build_audience_from_csv by focusing on mutation of existing audiences.

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 states when to use (for upload-type audiences) and when not (audiences built in LINE OA Manager UI are read-only). Provides guidance on mode selection and conditional parameter requirements.

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