Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Get LINE OA Report (multi-day digest)

line_get_oa_report
Read-onlyIdempotent

Get a LINE Official Account performance summary for any date range. Combines delivery, followers, demographics, and quota metrics into one digest report.

Instructions

Generate a digest of LINE OA performance over a date range. Bundles 8+ Insight API calls into a single Thai-friendly markdown report.

Args:

  • range: One of 'today' | 'yesterday' | 'this-week' | 'last-week' | 'this-month' | 'last-month', or { from: "YYYY-MM-DD", to: "YYYY-MM-DD" }. Default 'last-week'.

  • oa: optional OA id.

  • response_format: 'markdown' (default) | 'json'.

Returns (structured): { oa_id, range: { from, to, preset? }, delivery: { total, daily: [{ date, broadcast, multicast, push, reply, total }] }, followers: { latest_count?, follow?, unfollow?, net_gain? }, demographic_available: boolean, quota: { used, total, percentage_used }, notes: string[] // T-2 data lag note, privacy-floor note, etc. }

Notes:

  • LINE insight data has a T-2 lag (yesterday is the latest reliable date).

  • Insight is masked below the ~20-user privacy floor; report surfaces this.

  • Demographic only populated when the OA has enough consented friends.

Examples:

  • "สรุปสัปดาห์ที่แล้ว" → range: 'last-week'

  • "ดูข้อมูลเดือนนี้" → range: 'this-month'

  • "วิเคราะห์ 1-15 พ.ค." → range: { from: '2026-05-01', to: '2026-05-15' }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeNoDate range. Preset strings or { from: 'YYYY-MM-DD', to: 'YYYY-MM-DD' }.last-week
oaNo
response_formatNomarkdown
Behavior5/5

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

Annotations declare readOnlyHint, destructiveHint false, idempotentHint, openWorldHint. Description adds critical behavioral traits: T-2 data lag, privacy floor masking, demographic availability condition. 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.

Conciseness4/5

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

Well-structured with Args, Returns, Notes, Examples. Front-loaded with purpose. Slightly verbose but each section adds value. Could trim examples but reasonable length.

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?

No output schema, but description provides a detailed return structure. Covers all important aspects: data lag, privacy floor, demographic conditions. Given it bundles 8+ API calls, description is complete.

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?

Schema coverage 33% (only range described). Description compensates with examples, defaults, and explanation of oa and response_format. Adds meaning beyond enum list and default values.

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?

Title and description clearly state it generates a digest of LINE OA performance over a date range. Verb 'generate' and noun 'digest' with explicit detail on bundled API calls. Distinguishes from siblings like line_get_oa_status or line_get_message_stats.

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?

Description specifies when to use (multi-day digest, Thai-friendly markdown report). Notes on T-2 data lag and privacy floor guide proper use. Does not explicitly say when NOT to use or list alternatives, but context is clear.

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