Skip to main content
Glama
acquo

LINE Bot MCP Server (SSE Support)

by acquo

delete_rich_menu

Remove a rich menu from your LINE Official Account by specifying its ID to manage interface elements and maintain account organization.

Instructions

Delete a rich menu from your LINE Official Account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
richMenuIdYesThe ID of the rich menu to delete.

Implementation Reference

  • The handler for the 'delete_rich_menu' tool, which takes a richMenuId and calls the MessagingApiClient's deleteRichMenu method.
    server.tool(
      "delete_rich_menu",
      "Delete a rich menu from your LINE Official Account.",
      {
        richMenuId: richMenuIdSchema.describe(
          "The ID of the rich menu to delete.",
        ),
      },
      async ({ richMenuId }) => {
        try {
          const response = await this.client.deleteRichMenu(richMenuId);
          return createSuccessResponse(response);
        } catch (error) {
          return createErrorResponse(
            `Failed to delete rich menu: ${error.message}`,
          );
        }
      },
    );
  • The registration method for the DeleteRichMenu tool, which registers the tool with the MCP server.
    register(server: McpServer) {
      const richMenuIdSchema = z
        .string()
        .describe("The ID of the rich menu to delete.");
    
      server.tool(
        "delete_rich_menu",
        "Delete a rich menu from your LINE Official Account.",
        {
          richMenuId: richMenuIdSchema.describe(
            "The ID of the rich menu to delete.",
          ),
        },
        async ({ richMenuId }) => {
          try {
            const response = await this.client.deleteRichMenu(richMenuId);
            return createSuccessResponse(response);
          } catch (error) {
            return createErrorResponse(
              `Failed to delete rich menu: ${error.message}`,
            );
          }
        },
      );
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive operation, it doesn't specify whether this action is reversible, what permissions are required, whether there are rate limits, or what happens to associated data. This leaves significant behavioral gaps for a mutation tool.

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, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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

Completeness2/5

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

For a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address critical context like error conditions, return values, side effects, or how this tool relates to siblings (e.g., 'cancel_rich_menu_default'). The agent lacks sufficient information to use this tool safely and effectively.

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 schema description coverage is 100%, with the single parameter 'richMenuId' fully documented in the schema. The description doesn't add any parameter semantics beyond what the schema already provides, so it meets the baseline score of 3 for adequate but unenhanced parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 target resource ('a rich menu from your LINE Official Account'), making the purpose unambiguous. However, it doesn't differentiate this tool from sibling tools like 'cancel_rich_menu_default' or explain how deletion differs from cancellation, which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives like 'cancel_rich_menu_default' or what prerequisites might be needed (e.g., whether the rich menu must be inactive or unlinked first). It simply states what the tool does without contextual usage information.

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/acquo/line-bot-mcp-server-sse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server