Skip to main content
Glama
Sign In
line-desktop-mcp

line-desktop-mcp

by onlygummy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Log out of LINE

logout
DestructiveIdempotent

Signs only this MCP device out of LINE by invalidating and deleting the saved session, keeping archives and backups; other tools need a new login afterward.

Instructions

Log this device out of LINE and delete the saved session.

LINE is asked to invalidate the session first. If that request fails, the local file is deleted anyway, because the stored token is what matters. Your phone stays logged in: only this server's device is signed out, and the next login scans a fresh QR code.

The archive and the image backups are kept, so nothing that was already read is lost. Every tool still needs a login before it can reach LINE again, because the session file is what they run on.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "logout"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the failure mode: LINE is asked to invalidate first, but the local file is deleted even if that call fails. It also clarifies the blast radius — phone stays logged in, archive and image backups survive, but every sibling tool needs a new login — which is exactly the context destructiveHint alone cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and its effect, then layered with the failure behavior and consequences in short paragraphs. The closing clause about the session file being 'what they run on' mildly restates the earlier deletion point, costing a little tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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

For a zero-parameter, fully annotated, output-schema-backed mutation, this covers everything an agent needs: what is destroyed, what is preserved, what happens on partial failure, and what state the rest of the toolset is left in.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The description correctly spends no words on inputs.

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?

States a specific verb and resource — 'Log this device out of LINE and delete the saved session' — and scopes it to this device only, which cleanly separates it from the `login` sibling. An agent knows exactly what the tool does without opening the schema.

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

Usage Guidelines4/5

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

Implies the use case (ending this server's session) and explains the follow-up path via `login` scanning a fresh QR code, plus the important note that other tools will require re-authentication. It does not explicitly state when an agent should avoid logging out, so it falls just short of full when/when-not guidance.

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

Deploy Server

Other Tools