Skip to main content
Glama
acquo

LINE Bot MCP Server (SSE Support)

by acquo

cancel_rich_menu_default

Remove the default rich menu from a LINE Official Account to stop displaying it automatically to users.

Instructions

Cancel the default rich menu.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler that calls the LINE Messaging API to cancel the default rich menu.
    register(server: McpServer) {
      server.tool(
        "cancel_rich_menu_default",
        "Cancel the default rich menu.",
        {},
        async () => {
          const response = await this.client.cancelDefaultRichMenu();
          return createSuccessResponse(response);
        },
      );
  • src/index.ts:69-69 (registration)
    Registration of the cancel_rich_menu_default tool within the server.
    new CancelRichMenuDefault(messagingApiClient).register(server);
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Cancel' implies a mutation operation, but the description doesn't specify what happens when the default is canceled (does it revert to no default? does it affect existing users?), whether permissions are required, or if there are side effects. This leaves significant behavioral questions unanswered.

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 states exactly what the tool does with zero wasted words. It's appropriately sized for a simple, parameter-less operation and gets straight to the point without unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is minimally adequate but incomplete. It explains what action occurs but lacks crucial context about effects, permissions, or what happens after cancellation. Given the complexity of modifying system defaults, more behavioral information would be helpful for safe agent usage.

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?

With 0 parameters and 100% schema description coverage, the description appropriately doesn't need to explain parameters. The baseline for this scenario is 4 since there are no parameters to document, and the description correctly focuses on the tool's purpose rather than parameter details.

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 ('Cancel') and the resource ('default rich menu'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'set_rich_menu_default' beyond the opposite action, missing an opportunity to clarify their relationship more explicitly.

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. With a sibling tool 'set_rich_menu_default' that performs the opposite function, there's no indication of prerequisites, timing considerations, or what scenarios warrant canceling versus setting a default rich menu.

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