Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Estimate LINE send cost

line_estimate_send_cost
Read-onlyIdempotent

Estimate message quota cost for a planned send before execution, helping avoid exceeding limits when broadcasting or narrowcasting.

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
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds context: for audience targets, it looks up audience_count via line_list_audiences; for filter/everyone, it surfaces 'unknown' and recommends a dry run. No contradictions.

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?

The description is well-structured with clear Args, Returns, and Notes sections. It's informative without being overly verbose. Minor redundancy in the Notes section could be tightened, but overall very readable.

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?

The description fully explains the tool's behavior for all target types, including how estimation varies. It covers edge cases (unknown for filter/everyone), provides recommendations, and details the return object fields. No output schema exists, so the description handles it completely.

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 parameter schema has only 33% description coverage (only message_count has a schema description). The description's Args section adds meaning: explains target shapes by referencing line_send_message, and explains message_count's role in cost calculation. This compensates for the schema gap.

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?

Clearly states 'estimate how many quota messages a planned send will consume — without actually sending.' The description distinguishes this from the actual send operation, referencing line_send_message as a sibling, and specifies the use cases narrowcast/broadcast.

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?

Explicitly says 'without actually sending' and 'useful before user confirmation, especially for narrowcast / broadcast.' Also provides guidance on when exact estimation isn't possible and recommends using line_send_message for a dry run in those cases.

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