line-oa-mcp-ultimate

Manage LINE OA coupons

line_manage_coupon

Create, list, get, or discontinue LINE coupons. Converts dates to UNIX seconds and handles visibility settings.

Instructions

Coupon CRUD on a LINE OA (POST /v2/bot/coupon). modes: create (maps friendly inputs to LINE's schema — dates to UNIX seconds, visibility, etc.), list, get (by coupon_id), discontinue (ends a live coupon; irreversible — requires confirm=true). Deliver a created coupon via line_send_message message.coupon_id. Rate limit: shared 200 req/sec bucket with multicast.

Example: "Early Bird ลด 20% 1–8 มิ.ย." → { mode:"create", data:{ title:"Early Bird", discount_type:"percentage", discount_value:20, valid_from:"2026-06-01", valid_to:"2026-06-08", coupon_code:"EARLYBIRD" } }. "ปิด coupon C123" → { mode:"discontinue", coupon_id:"C123", confirm:true }.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`oa`	No
`data`	No	Required for mode='create'.
`mode`	Yes	create: make a new coupon; list: list all coupons; get: fetch one; discontinue: end one (irreversible).
`confirm`	No	Required true for mode='discontinue'.
`coupon_id`	No	Required for mode='get' or 'discontinue'.
`response_format`	No		markdown

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv1.1.0Jun 4, 2026

addedInput schema / properties / data / properties / acquisition_type

Added value: +{
+  "enum": [
+    "normal",
+    "lottery"
+  ],
+  "type": "string"
+}

addedInput schema / properties / data / properties / barcode_image_url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
changedInput schema / properties / data / properties / coupon_code / maxLength
```
Previous value: -20New value: +16
```
changedInput schema / properties / data / properties / description / maxLength
```
Previous value: -300New value: +1000
```

addedInput schema / properties / data / properties / discount_type

Added value: +{
+  "description": "percentage (default) | fixed (amount off) | explicit (before→after price).",
+  "enum": [
+    "percentage",
+    "fixed",
+    "explicit"
+  ],
+  "type": "string"
+}

addedInput schema / properties / data / properties / discount_value

Added value: +{
+  "description": "Percent (1–100) when percentage; currency amount when fixed.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

addedInput schema / properties / data / properties / lottery_probability

Added value: +{
+  "maximum": 99,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / data / properties / max_acquire_count
```
Added value: +{
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}
```

removedInput schema / properties / data / properties / max_redemptions

Removed value: -{
-  "exclusiveMinimum": 0,
-  "type": "integer"
-}

addedInput schema / properties / data / properties / max_use_per_ticket

Added value: +{
+  "description": "1 = once per user (default); -1 = unlimited.",
+  "enum": [
+    1,
+    -1
+  ],
+  "type": "number"
+}

addedInput schema / properties / data / properties / price_after

Added value: +{
+  "description": "Explicit only.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

addedInput schema / properties / data / properties / price_before

Added value: +{
+  "description": "Explicit only.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

removedInput schema / properties / data / properties / terms_url
```
Removed value: -{
-  "format": "uri",
-  "type": "string"
-}
```

addedInput schema / properties / data / properties / timezone

Added value: +{
+  "description": "LINE timezone enum, default ASIA_BANGKOK.",
+  "type": "string"
+}

changedInput schema / properties / data / properties / valid_from / description

Previous value: -"ISO datetime."New value: +"UNIX seconds, 'YYYY-MM-DD', or ISO datetime."

changedInput schema / properties / data / properties / valid_from / type
```
Previous value: -"string"New value: +[
+  "string",
+  "number"
+]
```

changedInput schema / properties / data / properties / valid_to / description

Previous value: -"ISO datetime."New value: +"UNIX seconds, 'YYYY-MM-DD', or ISO datetime."

changedInput schema / properties / data / properties / valid_to / type

Previous value: -"string"New value: +[
+  "string",
+  "number"
+]

addedInput schema / properties / data / properties / visibility

Added value: +{
+  "description": "PUBLIC = listed in LY services; UNLISTED (default) = link/broadcast only.",
+  "enum": [
+    "PUBLIC",
+    "UNLISTED"
+  ],
+  "type": "string"
+}

First observedv1.0.2May 29, 2026

TDQS

A4.2/5.0

Behavior1/5

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

Description states discontinue is 'irreversible' and requires confirm, but annotations have destructiveHint=false. This contradiction creates confusion for the agent, resulting in a score of 1 per evaluation rules.

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 bullet points and examples; every sentence adds value without redundancy. Front-loaded with core purpose and modes, then details and examples logically follow.

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?

Covers all key aspects: modes, parameter details, side effects (irreversible), rate limit, integration with sibling tools, and includes examples for common use cases. No gaps despite lack of output schema.

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?

Adds significant meaning beyond the input schema: explains default discount type, required fields for explicit mode, date format handling, and provides concrete examples that map friendly inputs to API expectations.

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?

Description explicitly states 'Coupon CRUD on a LINE OA' and enumerates four modes (create, list, get, discontinue), distinguishing it from sibling tools that handle rich menus, audiences, or messaging.

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?

Provides clear guidance on when to use each mode, includes an example for discontinue requiring confirm, and directs to line_send_message for delivery, effectively differentiating from alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Manage LINE OA coupons

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools