Skip to main content
Glama
acquo

LINE Bot MCP Server (SSE Support)

by acquo

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
NameRequiredDescriptionDefault
richMenuIdYesThe ID of the rich menu to set as default.

Implementation Reference

  • 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);
      },
    );
  • 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.",
      ),
    },
  • 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);
        },
      );
    }
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 ('set') but doesn't clarify if this is a mutation requiring specific permissions, whether it's reversible, or what happens on success/failure. For a tool that likely modifies system state, this is a significant gap in transparency.

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's front-loaded and wastes no space, making it easy for an agent 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?

Given the lack of annotations and output schema, the description is incomplete for a mutation tool. It doesn't explain behavioral aspects like error conditions, side effects, or return values, which are critical for an agent to use this tool correctly in context with its siblings.

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 the single parameter 'richMenuId' clearly documented. The description doesn't add any semantic details beyond what the schema provides (e.g., format examples or constraints), so it meets the baseline 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 resource ('rich menu as the default rich menu'), making the tool's purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'cancel_rich_menu_default' or 'get_rich_menu_list', which would require more specific context about when to use each.

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 'get_rich_menu_list'. It lacks context about prerequisites (e.g., whether a rich menu must exist) or scenarios where this operation is appropriate, leaving the agent to infer usage from tool names alone.

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