Skip to main content
Glama
Sign In
LINE Bot MCP Server

LINE Bot MCP Server

by pythoncdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete Rich Menu

delete_rich_menu
Destructive

Remove an existing rich menu from a LINE Official Account by its ID, helping you clean up or replace outdated menus.

Instructions

Delete a rich menu from your LINE Official Account.

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": {
      "richMenuId": "<richMenuId>"
    },
    "name": "delete_rich_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
richMenuIdYesThe ID of the rich menu to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1-local

TDQS

B3.3/5.0
Behavior2/5

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

The destructiveHint annotation already signals that this operation is destructive, but the description adds little behavioral context beyond that. It does not state permanence, whether deleting a default rich menu has side effects, or any account-level implications.

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 a single, clear, active sentence with no filler or redundant content. It aligns closely with the tool's purpose and is immediately scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description provides the essential operation and scope, but it does not mention side effects or special cases (e.g., deleting a default rich menu, irretrievability). Annotations cover the destructive nature, but the textual context remains thin.

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?

The only parameter, richMenuId, is fully described in the schema valence. The tool description does not add any detail about the expected format, where to find the ID, or how it is used beyond what the schema provides.

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 action ('Delete') and the resource ('a rich menu'), and it is scoped to the LINE account context. It unambiguously contrasts with sibling tools like create_rich_menu, get_rich_menu, or set_rich_menu_default.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives such as create_rich_menu or set_rich_menu_default. There is no mention of preconditions, when deletion should be avoided, or what happens if the rich menu is currently set as default.

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