Skip to main content
Glama
tndfame
by tndfame

delete_rich_menu

Remove a rich menu from your LINE Official Account by specifying its ID to manage messaging interface elements.

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 tool handler that deletes the specified rich menu ID using the LINE MessagingApiClient and returns success or error response.
    async ({ richMenuId }) => {
      try {
        const response = await this.client.deleteRichMenu(richMenuId);
        return createSuccessResponse(response);
      } catch (error) {
        return createErrorResponse(
          `Failed to delete rich menu: ${error.message}`,
        );
      }
    },
  • Registration of the 'delete_rich_menu' tool on the MCP server, including input schema, description, and handler function.
    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}`,
          );
        }
      },
    );
  • Zod schema definition for the 'richMenuId' input parameter.
    const richMenuIdSchema = z
      .string()
      .describe("The ID of the rich menu to delete.");
  • src/index.ts:68-68 (registration)
    Top-level instantiation and registration of the DeleteRichMenu class on the main MCP server instance.
    new DeleteRichMenu(messagingApiClient).register(server);
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. It states the action ('Delete') but doesn't mention permissions required, whether deletion is permanent/reversible, rate limits, or what happens to associated data. For a destructive operation with zero annotation coverage, this leaves critical gaps.

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 sentence that directly states the tool's purpose with no wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 tool with no annotations and no output schema, the description is insufficient. It doesn't explain behavioral implications (e.g., permanence, side effects) or return values, leaving the agent with incomplete context for safe invocation.

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?

Schema description coverage is 100%, with the single parameter 'richMenuId' fully documented in the schema. The description doesn't add any parameter details beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.

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 verb ('Delete') and resource ('a rich menu from your LINE Official Account'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'cancel_rich_menu_default' or 'set_rich_menu_default', which would require explicit comparison to earn a 5.

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?

No guidance is provided on when to use this tool versus alternatives like 'cancel_rich_menu_default' or 'set_rich_menu_default', nor are prerequisites or exclusions mentioned. The description only states what the tool does, not when it should be selected.

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/tndfame/mcp_management'

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