@zients/line-mcp-server

Get Room Member Profile

get_room_member_profile

Retrieve a LINE group member's profile by providing the room ID and user ID. The bot must be a member of the room.

Instructions

Get a member's profile in a LINE multi-person chat room. The bot must be a member of the room.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "roomId": "<roomId>",
      "userId": "<userId>"
    },
    "name": "get_room_member_profile"
  }
}

Input Schema

Name	Required	Description	Default
`roomId`	Yes	LINE Room ID (starts with "R")
`userId`	Yes	LINE User ID (starts with "U")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Sep 4, 2026

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses the membership prerequisite but does not mention the read-only nature, error conditions (e.g., if the bot is not a member), or return format. It adds some useful context but lacks comprehensive behavioral disclosure.

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, front-loaded sentence that states the purpose and a critical prerequisite. There is no redundancy or filler, making it highly concise and efficient.

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?

While the tool is simple (2 parameters, no output schema), the description lacks guidance on when to choose this tool over similar siblings and does not describe the profile fields returned. The prerequisite is helpful but the description is not fully complete for an agent to confidently select and invoke the correct tool.

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 describes both parameters fully (roomId and userId with format hints). The tool description adds no additional parameter information, so with 100% schema coverage the baseline of 3 applies.

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 verb 'Get' and the resource 'a member's profile in a LINE multi-person chat room', distinguishing it from sibling tools like get_group_member_profile (for groups) and get_user_profile (general user). The scope is specific and unambiguous.

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 provides a key prerequisite ('The bot must be a member of the room') but does not explicitly guide when to use this tool versus siblings such as get_group_member_profile or get_user_profile. The usage is implied by the room context, but no alternatives or exclusions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server