Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Build LINE Rich Menu (single panel)

line_build_rich_menu

Create a LINE Rich Menu in one call, combining validation, image upload, and default setting, with automatic API domain switching.

Instructions

Create a LINE Rich Menu in one call: validate → create → upload image → set as default. Collapses what is normally 4 LINE API calls into one tool, including the api-data.line.me domain switch for image upload (the #1 cause of failed implementations).

This V1 supports single-panel rich menus. The "tab-pair" (Tab A ↔ Tab B switching design) shipped widely by Thai agencies will be added in V1.1 alongside richmenu alias support.

Args:

  • name: Internal admin name (≤300 chars).

  • chat_bar_text: Label on the chat-bar button (≤14 chars). Show in user's LINE UI.

  • size: 'compact' (2500x843) or 'large' (2500x1686, default).

  • image_url: Public HTTPS URL of the rich menu image. JPEG/PNG, aspect ≥1.45, ≤1MB.

  • areas: Tappable regions with action objects (postback / message / uri / richmenuswitch).

  • set_as_default: Set as account-wide default after creation. Default true.

  • selected: Whether the menu auto-opens. Default true.

  • oa: Optional OA id.

Returns: { rich_menu_id: string, name: string, set_as_default: boolean, warnings: string[] }

Image requirements (validated client-side before upload):

  • Width: 800-2500px

  • Aspect ratio: ≥1.45

  • File size: ≤1MB

  • Format: JPEG or PNG

Examples:

  • "Rich Menu โปรวันแม่ 2 ปุ่ม" → params with 2 areas, large size, set_as_default: true

Errors:

  • INVALID_AREA → Coordinates exceed image bounds

  • IMAGE_TOO_LARGE → ≥1MB; resize and retry

  • QUOTA_EXCEEDED → 1,000 rich menus max per OA

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesInternal name (admin-only).
chat_bar_textYesThe button label shown in chat bar.
sizeNocompact (2500x843) for a single row, large (2500x1686) for a full panel. Default 'large'.large
image_urlYesPublic HTTPS URL of the rich menu image. Must be JPEG or PNG, aspect ratio ≥ 1.45, ≤1MB.
areasYesTappable areas. Coordinates are in image pixels.
set_as_defaultNoSet this rich menu as the account-wide default. Default true.
selectedNoWhether the rich menu opens by default when chat is opened.
oaNo
Behavior5/5

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

Annotations indicate non-readOnly, non-destructive, non-idempotent, openWorld. Description adds multi-step process, client-side validation, common errors (INVALID_AREA, IMAGE_TOO_LARGE, QUOTA_EXCEEDED), and the mandatory domain switch. Discloses default behaviors (set_as_default: true, selected: true). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Well-structured: summary, process explanation, version notes, parameter list, return type, validation, examples, errors. Slightly redundant with schema (e.g., image requirements), but front-loaded and efficient overall.

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 creation process, parameters, return value, validation, errors, examples. Could mention that multiple calls create multiple distinct menus (no idempotency), but given annotations and sibling tools, it's sufficiently complete.

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

Parameters3/5

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

Schema coverage is high (88%). Description adds minor context (e.g., 'Internal admin name', 'show in user's LINE UI') but mostly restates schema descriptions. Does not significantly add new 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?

Clearly states it creates a LINE Rich Menu in one call, collapsing 4 API steps. Distinguishes from siblings like line_delete_rich_menu, line_link_rich_menu by focusing on creation. Verb 'create' and specific resource 'LINE Rich Menu' are present.

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?

Describes when to use: to create a rich menu in one call, handling validation, upload, and default setting. Mentions common failure point (domain switch). Lacks explicit when-not-to-use, but context makes it clear compared to sibling tools.

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