Skip to main content
Glama
Sign In
line-oa-mcp-ultimate

line-oa-mcp-ultimate

by wasintoh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete LINE Rich Menu

line_delete_rich_menu
DestructiveIdempotent

Delete a rich menu by ID using confirmation to prevent irreversible removal. Links to users break silently, so audit before deletion.

Instructions

Delete a rich menu by ID. Requires confirm=true (guards against prompt drift). If the menu is linked to specific users those links break silently — consider line_audit_user_menu first.

Returns { success, deleted_id }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rich_menu_id": "<rich_menu_id>"
    },
    "name": "line_delete_rich_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
oaNo
confirmNoRequired true. Deletion is irreversible.
rich_menu_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate destructive and write operations. Description adds specific side effects: silent breaking of user links, the need for confirm flag, and return shape. This goes beyond annotations, though idempotency is not discussed.

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?

Three sentences, no fluff. Nearly every word adds value. Sentences are well-ordered: action, requirement, side-effect/alternative, return. Front-loaded with key info.

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?

Despite no output schema, the description covers return format, side effects, and prerequisite. Missing explanation of 'oa' parameter, but overall complete for a simple deletion tool with good annotations.

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

Parameters2/5

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

Schema coverage is low (33%). The description adds context only for 'confirm' (guards against prompt drift) but does not explain 'oa' or 'rich_menu_id' beyond what schema provides. The return value is mentioned but not parameter semantics.

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 'Delete a rich menu by ID' and distinguishes it from siblings like build, list, audit, and link tools. The purpose is specific and unambiguous.

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 explicit when-to-use: requires confirm=true. Warns against using when menu is linked to users without auditing, and suggests alternative tool line_audit_user_menu. Excellent guidance.

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

Deploy Server

Other Tools