Skip to main content
Glama
acquo

LINE Bot MCP Server (SSE Support)

by acquo

get_profile

Retrieve LINE user profile details including display name, profile picture URL, status message, and language for LINE Official Account management.

Instructions

Get detailed profile information of a LINE user including display name, profile picture URL, status message and language.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdNoThe user ID to get a profile. Defaults to DESTINATION_USER_ID.

Implementation Reference

  • The handler implementation for the "get_profile" tool.
    server.tool(
      "get_profile",
      "Get detailed profile information of a LINE user including display name, profile picture URL, status message and language.",
      {
        userId: userIdSchema,
      },
      async ({ userId }) => {
        if (!userId) {
          return createErrorResponse(NO_USER_ID_ERROR);
        }
    
        try {
          const response = await this.client.getProfile(userId);
          return createSuccessResponse(response);
        } catch (error) {
          return createErrorResponse(`Failed to get profile: ${error.message}`);
        }
      },
    );
  • The registration of the "get_profile" tool within the McpServer.
    register(server: McpServer) {
      const userIdSchema = z
        .string()
        .default(this.destinationId)
        .describe(
          "The user ID to get a profile. Defaults to DESTINATION_USER_ID.",
        );
    
      server.tool(
        "get_profile",
        "Get detailed profile information of a LINE user including display name, profile picture URL, status message and language.",
        {
          userId: userIdSchema,
        },
        async ({ userId }) => {
          if (!userId) {
            return createErrorResponse(NO_USER_ID_ERROR);
          }
    
          try {
            const response = await this.client.getProfile(userId);
            return createSuccessResponse(response);
          } catch (error) {
            return createErrorResponse(`Failed to get profile: ${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 what information is returned but doesn't mention important behavioral aspects: whether this requires specific permissions/authentication, rate limits, error conditions, or what happens when userId is omitted (defaults to DESTINATION_USER_ID per schema). For a user data retrieval tool with zero annotation coverage, this leaves significant 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, well-structured sentence that efficiently communicates the tool's purpose and scope. It lists the specific information returned without unnecessary elaboration. Every word earns its place, making it appropriately sized and front-loaded.

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 simple read operation with 1 parameter (100% schema coverage) but no annotations or output schema, the description is adequate but incomplete. It specifies what data is returned but doesn't cover behavioral aspects like authentication requirements, error handling, or response format. Given the tool's low complexity, it's minimally viable but could provide more context about the operation's constraints.

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?

Schema description coverage is 100%, so the schema already documents the userId parameter with its default behavior. The description doesn't add any parameter-specific information beyond what's in the schema. It mentions 'LINE user' which provides domain context but no additional parameter semantics. Baseline 3 is appropriate when schema does the heavy lifting.

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 tool's purpose: 'Get detailed profile information of a LINE user' with specific attributes listed (display name, profile picture URL, status message, language). It distinguishes itself from siblings by focusing on user profile retrieval rather than messaging or rich menu operations. However, it doesn't explicitly contrast with potential similar tools like 'get_user' or 'get_user_info' if they existed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying it retrieves LINE user profiles, but provides no explicit guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like authentication requirements) or compare with other user-related operations. The context is clear but lacks specific when/when-not instructions.

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