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 with a single call: validate, create, upload image, and set as default. Combines multiple API steps into one action.

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
Behavior4/5

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

Annotations show readOnlyHint=false, matching the mutative nature. The description adds behavioral details: it collapses 4 API calls, validates client-side, and sets default. It also explains error conditions like QUOTA_EXCEEDED.

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

Conciseness3/5

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

The description is well-structured with sections but is quite long and repeats some information (image requirements in args and separately). A bit more conciseness would improve it.

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?

Given no output schema, the description includes return structure and error types. It covers workflow, constraints, and examples adequately for an agent to use the tool correctly.

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%), so baseline is 3. The description adds some context beyond schema (e.g., image requirements validated client-side, error examples), but the schema already describes parameters well.

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 the tool's purpose: 'Create a LINE Rich Menu in one call' and details the steps (validate→create→upload image→set as default). It distinguishes from sibling tools like line_delete_rich_menu and line_list_rich_menus by focusing on creation.

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?

The description provides context on when to use (creating rich menus) and highlights a common pitfall (domain switch for image upload). It notes upcoming features (tab-pair in V1.1) but does not explicitly compare with alternatives among siblings.

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