Skip to main content
Glama
tndfame
by tndfame

get_profile

Retrieve LINE user profile details including display name, profile picture URL, status message, and language settings for personalized interactions.

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.U1a2b3c4d5e6f7g8h9i0j1k2l3m4n5o6p

Implementation Reference

  • The handler function that fetches the LINE user profile using the provided userId, handles missing userId errors, and returns formatted success or error responses.
      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}`);
        }
      },
    );
  • Zod schema definition for the optional 'userId' input parameter, defaulting to the destination user ID.
    const userIdSchema = z
      .string()
      .default(this.destinationId)
      .describe(
        "The user ID to get a profile. Defaults to DESTINATION_USER_ID.",
      );
  • Core registration of the 'get_profile' tool on the MCP server within the GetProfile class's register method, including name, description, schema, and handler.
    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}`);
        }
      },
    );
  • src/index.ts:65-65 (registration)
    Instantiates the GetProfile tool with MessagingApiClient and destinationId, then invokes its register method to add the tool to the MCP server.
    new GetProfile(messagingApiClient, destinationId).register(server);
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 implies a read-only operation but does not specify authentication requirements, rate limits, error conditions, or response format details. For a tool with zero annotation coverage, this leaves significant behavioral 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, efficient sentence that front-loads the core purpose and lists key return fields without unnecessary elaboration. Every word contributes directly to understanding the tool's function, making it highly concise and well-structured.

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 low complexity (one parameter, no output schema) and high schema coverage, the description is adequate but incomplete. It lacks behavioral details (e.g., authentication, errors) that are crucial for a tool with no annotations, though the purpose and parameters are clear.

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 fully documents the single parameter (userId). The description adds no additional parameter semantics beyond what the schema provides, such as format constraints or usage examples, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get detailed profile information') and resource ('LINE user'), listing the exact data fields returned (display name, profile picture URL, status message, language). It distinguishes this from sibling tools that focus on messaging, database queries, or rich menus, making the purpose unambiguous.

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 does not mention prerequisites (e.g., user ID availability), exclusions, or related tools for similar purposes, leaving the agent to infer usage context solely from the tool name and description.

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