LINE Bot MCP Server (SSE Support)

by acquo

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

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

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools/cancelRichMenuDefault.ts:14-23 (handler)

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);
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1-localMar 19, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Cancel' implies a mutation operation, but the description doesn't specify whether this requires special permissions, what happens after cancellation (e.g., does it revert to a previous state?), or potential side effects. This leaves significant behavioral 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, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential information 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 states what the tool does but lacks behavioral context (permissions, effects, return values) that would be helpful given the tool's complexity as a system configuration change.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for this zero-parameter tool.

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 target resource ('default rich menu'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'delete_rich_menu' or 'set_rich_menu_default', which would require explicit comparison to achieve 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 'set_rich_menu_default' or 'delete_rich_menu'. There's no mention of prerequisites, context, or exclusions, leaving the agent without usage direction.

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

Deploy Server