Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Get LINE OA Status

line_get_oa_status
Read-onlyIdempotent

Retrieve friend count, quota usage, webhook status, and default rich menu for a LINE Official Account in one call. Use this health check to guide subsequent actions.

Instructions

Quick health check of a LINE Official Account: friend count, monthly quota usage, webhook status, and current default rich menu. Aggregates 4 LINE API calls into one card.

Use this as the first call of a session — every other tool decision (whether to send, schedule, switch OA, etc.) benefits from knowing current quota and webhook state.

Args:

  • oa (string, optional): OA id from multi-OA config. Default = active OA.

  • response_format ('markdown' | 'json'): Output format. Default 'markdown'.

Returns: Structured object: { oa: { id, display_name, picture_url? }, friends?: number, // omitted if not retrievable quota: { used, total, remaining, percentage_used }, webhook: { active, url? }, default_rich_menu?: { id, name? }, region?: string, health: 'OK' | 'WARNING' | 'ERROR', warnings: string[] }

Examples:

  • "ดูสถานะ OA หน่อย" → call with no args

  • "Status ของ Client A" → { oa: "client_a" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
oaNoOptional OA id from the multi-OA config. Omit to use the active/default OA.
response_formatNoOutput format. 'markdown' is human-readable; 'json' is structured.markdown
Behavior5/5

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

Beyond readOnlyHint and idempotentHint, the description details that it aggregates 4 API calls, lists return fields (including optional friends), and explains behavior like omission of friends if not retrievable. 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?

Well-structured with sections (Args, Returns, Examples) and front-loaded with purpose. Slightly lengthy due to return object, but every part adds value.

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 fully documents the return structure with field descriptions. Examples and context on when to use make it complete for a health-check tool.

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 covers both parameters fully. Description adds value by explaining default behavior for 'oa' (active OA) and showing the 'response_format' enum context. The return structure provides additional semantic context.

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 defines the tool as a quick health check aggregating friend count, quota, webhook, and rich menu status. It distinguishes itself from siblings by being a read-only informational aggregate.

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?

Explicitly recommends using this as the first call in a session, noting that other decisions benefit from its output. Lacks explicit when-not-to-use, 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