Skip to main content
Glama

line_search_messages

Search the text of recent LINE messages in one chat or across all chats to locate specific conversations and details.

Instructions

(Beta) Searches the text of your recent LINE messages, in one chat or in all.

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": "line_search_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses little: only a '(Beta)' caveat and a vague 'recent' window. It omits result caps, pagination, whether a connection is required, auth needs, and what a match looks like. The '(Beta)' marker is the one genuinely useful behavioral signal.

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?

A single tight sentence with the beta flag and the core action front-loaded; nothing is padded. The scope clause is slightly misleading given the empty schema, but it is not verbose.

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

Completeness2/5

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

For a search tool with no parameters, no output schema, and no annotations, the description leaves too much open: how recency is bounded, how many results return, how to target a single chat, and whether connection state matters. An agent could invoke it but could not predict its behavior or interpret results confidently.

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?

With zero parameters the baseline would be 4, but the description advertises scoping 'in one chat or in all' while the input schema declares no properties at all. That dangling reference creates confusion about how chat scoping is expressed, so it falls below the zero-parameter baseline rather than above it.

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?

States a specific verb and resource: 'Searches the text of your recent LINE messages', which is clearly distinguishable from reading messages. It also states the scope ('in one chat or in all'). It stops short of naming the read-vs-search sibling distinction explicitly, but the purpose is 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 word 'recent' and the phrase 'text of your messages' imply this is a keyword lookup over recent history rather than a full read, which implicitly contrasts with line_read_messages. However, there is no explicit when-to-use/when-not guidance and no mention of prerequisites such as an active LINE connection.

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