Skip to main content
Glama
tndfame
by tndfame

get_rich_menu_list

Retrieve all rich menus from your LINE Official Account to manage interactive message interfaces for user engagement.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that fetches the rich menu list using the LINE Messaging API client and returns a success or error response.
      async () => {
        try {
          const response = await this.client.getRichMenuList();
          return createSuccessResponse(response);
        } catch (error) {
          return createErrorResponse(
            `Failed to broadcast message: ${error.message}`,
          );
        }
      },
    );
  • Registers the 'get_rich_menu_list' tool with MCP server, including name, description, empty input schema, and the handler function.
    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}`,
          );
        }
      },
    );
  • src/index.ts:67-67 (registration)
    Instantiates the GetRichMenuList class with the messaging API client and calls its register method to add the tool to the main MCP server.
    new GetRichMenuList(messagingApiClient).register(server);
  • src/index.ts:32-32 (registration)
    Imports the GetRichMenuList tool implementation.
    import GetRichMenuList from "./tools/getRichMenuList.js";
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 mentions retrieving a list but doesn't specify whether this is a read-only operation, if authentication is required, potential rate limits, or the format of the returned data. This leaves significant gaps for an agent to understand the tool's behavior.

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 that efficiently conveys the core functionality without any redundant information. It is appropriately sized and front-loaded, 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema), the description adequately covers the basic purpose. However, without annotations or output schema, it lacks details on behavioral aspects like authentication needs or return format, which could be important for an agent to use it correctly in context.

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, focusing instead on the tool's purpose. A baseline of 4 is applied since no parameters exist to document.

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'), providing a specific purpose. However, it doesn't explicitly differentiate from sibling tools like 'get_profile' or 'get_message_quota', 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?

The description provides no guidance on when to use this tool versus alternatives like 'set_rich_menu_default' or 'delete_rich_menu', nor does it mention prerequisites or context for usage. It simply states what the tool does without indicating appropriate scenarios.

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/tndfame/mcp_management'

If you have feedback or need assistance with the MCP directory API, please join our Discord server