Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Manage LIFF apps

line_manage_liff_app

Manage LIFF app lifecycle on your LINE channel. Create, list, update, or delete LIFF apps using simple commands.

Instructions

LIFF lifecycle CRUD. Four modes:

  • create: New LIFF app. Requires config.view (type + url).

  • list: List all LIFF apps on the channel.

  • update: Modify an existing LIFF app. Requires liff_id + partial config.

  • delete: Remove a LIFF app. Requires liff_id + confirm=true.

Args:

  • mode: 'create' | 'list' | 'update' | 'delete'.

  • liff_id: required for update / delete.

  • config: full for create, partial for update.

  • confirm: required true for delete.

  • oa: optional OA id.

Auth note: LIFF Server API uses LINE Login channel tokens — V1 uses the same Messaging API token for simplicity. For separate-channel setups, see docs.

Examples:

  • "สร้าง LIFF tall https://my.app" → { mode: "create", config: { view: { type: "tall", url: "https://my.app" } } }

  • "ดู LIFF apps ทั้งหมด" → { mode: "list" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
liff_idNoRequired for update / delete.
configNoRequired for create. Partial for update.
confirmNo
oaNo
Behavior4/5

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

Discloses auth token requirements and the need for confirm=true in delete mode, adding context beyond annotations. No contradiction with annotations, though destructiveHint=false is slightly mitigated by the confirm requirement.

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?

Concise and well-structured with bullet points and examples. Every sentence adds value without redundancy.

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

Completeness4/5

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

Covers all modes, required args, and auth context. Missing return value info (no output schema) and some parameter details (e.g., 'oa'). Still fairly complete for a CRUD tool.

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?

Compensates for low schema coverage (40%) by explaining mode meanings, parameter requirements per mode, config structure, and providing natural language examples. Greatly enhances understanding.

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 manages LIFF app lifecycle with four specific modes (create, list, update, delete). It distinguishes the tool's purpose from sibling tools, none of which cover LIFF operations.

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 clear guidance per mode, including required parameters and examples. Does not explicitly state when not to use this tool, but given no direct alternatives, this is acceptable.

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