Skip to main content
Glama
acquo

LINE Bot MCP Server (SSE Support)

by acquo

get_rich_menu_list

Retrieve all rich menus configured for your LINE Official Account to manage interactive message interfaces.

Instructions

Get the list of rich menus associated with your LINE Official Account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic by calling the LINE Messaging API client to retrieve the rich menu list.
      async () => {
        try {
          const response = await this.client.getRichMenuList();
          return createSuccessResponse(response);
        } catch (error) {
          return createErrorResponse(
            `Failed to broadcast message: ${error.message}`,
          );
        }
      },
    );
  • The registration method that registers the tool with the MCP server.
    register(server: McpServer) {
      server.tool(
        "get_rich_menu_list",
        "Get the list of rich menus associated with your LINE Official Account.",
        {},
        async () => {
          try {
            const response = await this.client.getRichMenuList();
            return createSuccessResponse(response);
          } catch (error) {
            return createErrorResponse(
              `Failed to broadcast message: ${error.message}`,
            );
          }
        },
      );
    }
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. It states it 'gets' a list, implying a read-only operation, but doesn't clarify permissions, rate limits, pagination, or what happens if no rich menus exist. This leaves significant gaps for a tool that likely interacts with an external API.

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 with zero waste. It's front-loaded with the core action and resource, making it efficient and easy to parse for an AI agent.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the returned list contains (e.g., menu IDs, names, structures), error conditions, or behavioral traits like authentication needs. For a tool that likely returns structured data from an external service, this leaves the agent under-informed.

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 high baseline score for not adding unnecessary information.

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 ('Get the list') and resource ('rich menus associated with your LINE Official Account'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_profile' or 'get_message_quota' that also retrieve information, so it misses full sibling distinction.

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. It doesn't mention prerequisites, context (e.g., before setting or deleting rich menus), or exclusions, leaving the agent to infer usage from the tool name 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