Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Upload / replace a LINE rich menu image

line_upload_rich_menu_image
Idempotent

Replace a rich menu image while preserving its layout, tap areas, and links. Downloads a public image URL, validates format and size, then uploads the new image.

Instructions

Replace the image on an EXISTING rich menu without recreating it — the richMenuId, tappable areas, and any per-user links are preserved. Downloads the image from a public HTTPS URL, validates format + size, then uploads to the api-data.line.me content endpoint (the domain switch that trips up most implementations).

Args:

  • rich_menu_id: ID of the existing rich menu to update.

  • image_url: Public HTTPS URL of the new image. JPEG/PNG, ≤1MB.

  • oa: Optional OA id.

Returns: { rich_menu_id: string, uploaded: true, bytes: number // size of the uploaded image }

Image requirements (validated client-side before upload):

  • Format: JPEG or PNG

  • File size: ≤1MB

Examples:

  • "เปลี่ยนรูป rich menu R123 เป็นแบนเนอร์ใหม่" → { rich_menu_id: "R123", image_url: "https://.../banner.png" }

Errors:

  • image_url not reachable → returns download error

  • unsupported format → returns format error

  • IMAGE_TOO_LARGE → ≥1MB; compress and retry

  • 404 → rich_menu_id not found

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rich_menu_idYesID of the existing rich menu whose image will be replaced.
image_urlYesPublic HTTPS URL of the new image. Must be JPEG or PNG, ≤1MB.
oaNoOptional OA id; defaults to active OA.
Behavior5/5

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

Annotations provide idempotentHint=true, and the description adds detail: downloads from a public HTTPS URL, validates format and size, uploads to a specific endpoint, and preserves existing settings. No contradictions with annotations.

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?

The description is well-structured with sections for Args, Returns, Image requirements, Examples, Errors. Each sentence is informative and necessary. Key point is front-loaded.

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 tool with 3 parameters and no output schema, the description covers purpose, parameters, return format, error handling, and usage context. It is fully sufficient for an agent to invoke correctly.

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

Parameters4/5

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

Input schema covers all parameters with descriptions. The description adds value by specifying that image_url must be public HTTPS and providing examples. Although schema coverage is 100%, the extra context (e.g., domain switch issue) 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 'Replace the image on an EXISTING rich menu without recreating it', specifying the action (upload/replace) and the resource (rich menu image). It distinguishes from sibling tools like line_build_rich_menu and line_delete_rich_menu by focusing on image replacement.

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 explains when to use the tool (replacing an image without recreating) and what is preserved (richMenuId, tappable areas, per-user links). It also lists common errors and retry guidance. However, it lacks explicit comparison to alternatives or when not to 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