Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Run a tool across many LINE OAs

line_run_on_many_oas
Read-onlyIdempotent

Run read-only LINE OA tools across multiple accounts simultaneously, isolating individual errors to prevent full failure.

Instructions

Agency feature — run any read-only line_* tool across many OAs in parallel. Errors on individual OAs are isolated (one bad token doesn't break the whole run).

Supported tools (read-only only for V1 safety):

  • line_get_oa_status

  • line_get_oa_report

  • line_list_audiences

  • line_list_rich_menus

  • line_test_webhook

Args:

  • tool: One of the supported tool names.

  • oa_ids: Array of OA ids, or 'all' (default).

  • parallel: Max concurrency 1-10 (default 5).

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

Returns: { tool, count_ok, count_failed, results: [{ oa_id, oa_name, success, summary }], errors: [{ oa_id, error }] }

Examples:

  • "เช็คสถานะทุก OA" → { tool: "line_get_oa_status", oa_ids: "all" }

  • "ทดสอบ webhook ทุก client" → { tool: "line_test_webhook" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYesRead-only tool to run across all selected OAs. Write tools (send/build/delete) are not supported in bulk mode for safety.
oa_idsNoEither an array of OA ids or 'all' to use every configured OA. Default 'all'.all
parallelNoMax concurrent OAs (1-10). Default 5.
response_formatNomarkdown
Behavior5/5

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

The description discloses concurrency limits, error isolation, and supported tools. Annotations already indicate read-only and idempotent, but the description adds valuable detail about behavior beyond annotations, with 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.

Conciseness5/5

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

The description is well-structured with sections, bullet points, and examples. Every sentence adds value, and it is appropriately concise for the complexity of the tool.

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?

Given the schema coverage and annotations, the description is complete: it explains return format, error handling, concurrency, and usage context. No gaps remain for an agent to invoke correctly.

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 is 75%, and the description adds clarity by listing supported tools and providing usage examples. The description complements the schema well without redundancy.

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 explicitly states the tool runs read-only line_* tools across many OAs in parallel, listing five specific tools. This clearly differentiates it from sibling tools that operate on single OAs or perform write operations.

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?

The description states it's for read-only tools only, mentions error isolation, and provides examples. It doesn't explicitly mention when not to use, but the context is clear. Could be improved by explicitly naming alternative bulk write tools, but it's still strong.

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