Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Manage LINE rich menu aliases (tab switching)

line_manage_rich_menu_alias

Create, update, delete, get, or list rich menu aliases to swap displayed panels instantly on your LINE Official Account.

Instructions

Rich menu alias CRUD. Aliases power tab-switching rich menus: a 'richmenuswitch' action references a richMenuAliasId, and repointing that alias at a different rich menu swaps the displayed panel instantly — no per-user re-linking. Five modes:

  • create: Bind a new alias_id to a rich_menu_id.

  • update: Repoint an existing alias to a different rich_menu_id.

  • delete: Remove an alias (does not delete the underlying rich menu).

  • get: Fetch a single alias by alias_id.

  • list: List all aliases on the OA.

Args:

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

  • alias_id: Required for all modes except 'list'.

  • rich_menu_id: Required for 'create' and 'update'.

  • oa: Optional OA id.

Returns:

  • create/update/delete → { mode, alias_id, rich_menu_id? }

  • get → { richMenuAliasId, richMenuId }

  • list → { aliases: { richMenuAliasId, richMenuId }[] }

Examples:

  • "สร้าง alias tab-a ชี้ไป R123" → { mode: "create", alias_id: "tab-a", rich_menu_id: "R123" }

  • "เปลี่ยน alias tab-a ไปที่ R456" → { mode: "update", alias_id: "tab-a", rich_menu_id: "R456" }

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

  • "ลบ alias tab-a" → { mode: "delete", alias_id: "tab-a" }

Errors:

  • missing alias_id (non-list modes) / missing rich_menu_id (create/update) → returns input error

  • 400 → alias_id already exists (create)

  • 404 → alias not found (update/delete/get)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYescreate: bind a new alias→menu; update: repoint an alias to another menu; delete: remove an alias; get: fetch one; list: list all.
alias_idNoThe rich menu alias ID. Required for all modes except 'list'.
rich_menu_idNoRich menu ID the alias points to. Required for mode='create' and 'update'.
oaNoOptional OA id; defaults to active OA.
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description explains mutations (create/update/delete) vs reads (get/list). It clarifies that delete does not remove the underlying rich menu and lists error responses, adding value beyond annotations.

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?

The description is well-organized with sections for modes, args, returns, examples, and errors. While slightly verbose, every section adds value and is front-loaded with the core concept.

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?

For a complex CRUD tool with 5 modes and 4 parameters, the description covers all behaviors, parameters, return types, and error cases. No output schema exists, but the description adequately documents outputs. Sibling tools are distinct, so no missing context.

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?

Schema coverage is 100%, and the description richly explains each parameter with textual descriptions, mode-specific requirements, and examples. It clarifies the meaning of alias_id and rich_menu_id in context and details return values per mode.

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 LINE rich menu aliases for tab-switching. It explains the concept and distinguishes from sibling tools like line_link_rich_menu by focusing solely on alias CRUD 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?

The description details the five modes and includes examples and error handling. While it doesn't explicitly compare to alternatives, the specialized nature and clear mode explanations guide proper use.

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