Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Estimate LINE send cost

line_estimate_send_cost
Read-onlyIdempotent

Estimate how many quota messages a planned send will consume without actually sending. Useful for cost checks before user confirmation, especially for narrowcast or broadcast.

Instructions

Estimate how many quota messages a planned send will consume — without actually sending. Useful before user confirmation, especially for narrowcast / broadcast.

Args:

  • target: Same shapes as line_send_message ({ user_id } | { user_ids } | { audience } | { filter } | { everyone: true }).

  • message_count: How many message objects in the send (1-5, default 1). LINE charges per message * recipients.

  • oa: optional OA id.

Returns: { estimated_recipients?: number, // known exactly for user_id(s); approximate for audience; unknown for filter/everyone estimated_cost_messages?: number, // recipients * message_count quota: { used, total, remaining, percentage_used }, cost_share_percent?: number, // estimated_cost / remaining notes: string[] }

Notes:

  • For target.audience: we look up audience_count via line_list_audiences first.

  • For target.filter or target.everyone: exact estimation isn't possible from API alone — we surface "unknown" and recommend a dry_run via line_send_message instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYes
message_countNoNumber of messages in the send (LINE counts each message in a batch). Default 1.
oaNo
Behavior5/5

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

Annotations already indicate read-only, non-destructive, idempotent. The description adds behavioral details: no actual send, lookups audience_count for target.audience, and notes limitations for filter/everyone. No contradiction.

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 well-organized with Args, Returns, Notes sections. Each sentence adds value without redundancy. It is concise yet complete.

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?

Despite no output schema, the description details return format and explains estimated fields. It also covers edge cases and references sibling tools (line_list_audiences, line_send_message). The tool is complex but the description is thorough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% (message_count has description). The description provides extensive meaning for target (explains all shapes and behaviors) and adds context for message_count and oa, compensating fully.

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 tool estimates quota messages consumed by a planned send without sending, using specific verbs and resource ('estimate cost'). It distinguishes itself from line_send_message by emphasizing it does not send.

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

Usage Guidelines5/5

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

The description explicitly advises 'use before user confirmation, especially for narrowcast/broadcast' and provides guidance for filter/everyone targets, recommending a dry run via line_send_message for exact estimation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wasintoh/line-oa-mcp-ultimate'

If you have feedback or need assistance with the MCP directory API, please join our Discord server