Skip to main content
Glama

line_send_flex_message

Sends a rich Flex Message to a LINE user or group with fallback notification text, enabling structured content delivery in chats.

Instructions

Send a rich Flex Message to a LINE user or group.

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": {
      "to": "<to>",
      "alt_text": "<alt_text>",
      "contents": "<contents>"
    },
    "name": "line_send_flex_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
alt_textYesFallback text shown in push notifications
contentsYesFlex Message container as JSON object or string
channel_access_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.11
    • changedInput schema / required
      Previous value: -[
      -  "channel_access_token",
      -  "to",
      -  "alt_text",
      -  "contents"
      -]New value: +[
      +  "to",
      +  "alt_text",
      +  "contents"
      +]
  2. Addedv0.1.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states that a message is sent, but does not disclose authentication expectations for channel_access_token, recipient ID format, delivery constraints, failure modes, or whether it is push-style versus reply-style.

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 with no filler. It gets directly to the action and target without unnecessary repetition.

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 messaging mutation with no annotations, no output schema, and only half of the parameters documented in the schema, the description is too sparse. It omits key context an agent would need, such as authentication via channel_access_token, recipient identifier expectations, and delivery behavior.

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 coverage is only 50%, and the description partially compensates by clarifying that 'to' refers to a LINE user or group. However, it adds no semantics for channel_access_token, and recipient ID format remains unspecified. The alt_text and contents parameters are already documented in the schema.

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?

The description states a specific verb and resource: sending a rich Flex Message to a LINE user or group. The message type and target scope make the purpose clear, though it does not explicitly contrast with siblings such as line_send_message, line_reply_message, or line_broadcast.

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?

There is no explicit guidance on when to choose this tool over line_send_message, line_reply_message, or line_broadcast. The description only implies that it is for Flex Messages, leaving the agent to infer the selection criteria from the name and sibling list.

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