LINE Bot MCP Server (SSE Support)

Overview Schema Source Related Servers Discussions Admin

set_rich_menu_default

Set a rich menu as the default display for all users in LINE Bot conversations, ensuring consistent interface presentation.

Instructions

Set a rich menu as the default rich menu.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`richMenuId`	Yes	The ID of the rich menu to set as default.

Implementation Reference

src/tools/setRichMenuDefault.ts:28-32 (handler)

The handler function that executes the setRichMenuDefault tool logic using the LINE Messaging API client.

  async ({ richMenuId }) => {
    const response = await this.client.setDefaultRichMenu(richMenuId);
    return createSuccessResponse(response);
  },
);

src/tools/setRichMenuDefault.ts:23-27 (schema)
The schema definition for the set_rich_menu_default tool input parameters.
```
{
  richMenuId: richMenuIdSchema.describe(
    "The ID of the rich menu to set as default.",
  ),
},
```

src/tools/setRichMenuDefault.ts:15-33 (registration)

The registration logic for the set_rich_menu_default tool in the MCP server.

register(server: McpServer) {
  const richMenuIdSchema = z
    .string()
    .describe("The ID of the rich menu to set as default.");

  server.tool(
    "set_rich_menu_default",
    "Set a rich menu as the default rich menu.",
    {
      richMenuId: richMenuIdSchema.describe(
        "The ID of the rich menu to set as default.",
      ),
    },
    async ({ richMenuId }) => {
      const response = await this.client.setDefaultRichMenu(richMenuId);
      return createSuccessResponse(response);
    },
  );
}

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1-localMar 19, 2026

TDQS

C2.9/5.0

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 tool performs a 'set' action, implying mutation, but does not cover permissions needed, whether the change is reversible, error conditions, or what happens to the previous default. This leaves significant 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 unnecessary words. It is front-loaded and appropriately sized for a simple tool, with no wasted information.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects like side effects, return values, or error handling, which are critical for safe and effective use by an AI agent.

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 input schema has 100% description coverage, with 'richMenuId' clearly documented. The description does not add any additional meaning beyond the schema, such as format examples or constraints, so it meets the baseline score 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 action ('set') and the resource ('rich menu as the default rich menu'), making the purpose immediately understandable. However, it does not differentiate from sibling tools like 'cancel_rich_menu_default' or explain what 'default' means in this context, 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?

No guidance is provided on when to use this tool versus alternatives like 'cancel_rich_menu_default' or 'get_rich_menu_list', nor are prerequisites or context for setting a default rich menu mentioned. The description lacks any usage instructions or exclusions.

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

Deploy Server