@zients/line-mcp-server

Leave Room

leave_room

Removes the bot from a LINE multi-person chat room permanently, using the room ID.

Instructions

Leave a LINE multi-person chat room. Bot will leave the room permanently.

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>"
    },
    "name": "leave_room"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Sep 4, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description must carry the full behavioral transparency burden. It only notes that the bot leaves permanently, but omits details such as whether the operation is reversible, what happens if the bot is not a member, or any side effects. This is insufficient for a mutation tool.

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 concise, consisting of two short sentences. The first sentence states the core action, and the second adds a key detail (permanence). It is well-structured and front-loaded with the primary purpose.

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 tool with one parameter, the description is somewhat minimal. It does not mention the response or result (no output schema), nor any prerequisites or error conditions. While the action is straightforward, the lack of such context could lead to ambiguity in certain edge cases, so completeness is moderate.

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 schema already provides a description for roomId (LINE Room ID starting with 'R'), so coverage is 100%. The tool description does not add further meaning to the parameter, such as how to obtain it or any constraints. Given full schema coverage, the baseline of 3 is appropriate.

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 action ('Leave') and the specific resource ('LINE multi-person chat room'). It also notes the permanence of the action, which distinguishes it from temporary actions. The resource type is distinct from sibling tools like leave_group, 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 Guidelines3/5

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

The description does not explicitly state when to choose this tool over alternatives such as leave_group. It implicitly indicates the target is a room, but lacks a direct comparison or condition to guide the agent. Since the sibling list includes leave_group, more explicit selection criteria would be beneficial.

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

Deploy Server