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 any read-only LINE tool across multiple Official Accounts simultaneously. Errors on individual OAs are isolated, so a bad token won't break the whole run.

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

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds key behavioral details like error isolation (one bad token doesn't break the run), parallelism limits (default 5), and response format. 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?

Well-structured with sections, bullet points for supported tools, clear parameter list, and examples. Every sentence adds value, no fluff. Front-loaded with main purpose.

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 no output schema, the description fully explains the return structure, error handling, and usage context. Covers all aspects needed for correct invocation, including examples.

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 description adds meaning beyond schema by explaining the 'tool' parameter's read-only restriction, the 'oa_ids' default 'all', and providing examples. It also clarifies the 'response_format' default and 'parallel' max concurrency.

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 it runs read-only line_* tools across many OAs in parallel, with specific verb 'run a tool', a specific resource 'many LINE OAs', and lists supported tools, differentiating from individual sibling tools.

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 describes when to use (agency feature, bulk read-only operations) and when not to (write tools not supported for safety). Provides examples for context and lists alternatives (sibling tools are individual line_* tools).

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