Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Test LINE Webhook Endpoint

line_test_webhook
Idempotent

Ping LINE Official Account webhook URL from LINE servers and report HTTP status code, latency, and failure reasons like timeout or signature verification errors to debug bot issues.

Instructions

Ping the OA's webhook URL from LINE servers and report HTTP status + latency. LINE checks that the endpoint returns 200 within their timeout AND that signature verification works (when secret is configured).

Args:

  • override_endpoint: optional public HTTPS URL to test instead of the configured one.

  • oa: optional OA id.

Returns: { success: boolean, status_code: number, latency_ms?: number, reason: string, // LINE's human-readable result detail?: string, configured_endpoint?: string, tested_endpoint: string }

Common failure modes (LINE returns them via 'reason'):

  • INVALID_REPLY: webhook responded but the response shape is unexpected

  • UNAUTHORIZED: signature verification failed (your code uses wrong channel_secret)

  • SERVER_ERROR: webhook returned 5xx

  • TIMEOUT: webhook took >10s

  • SSL_ERROR: HTTPS cert problem

Use this whenever a bot stops responding before debugging anything else.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
override_endpointNoTest a specific URL instead of the OA's currently configured webhook URL.
oaNo
Behavior4/5

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

Annotations indicate idempotentHint=true and readOnlyHint=false. Description adds behavioral context such as signature verification checks, timeout details (10s), and common failure modes, supplementing the annotations without contradiction.

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 efficiently structured with a summary sentence, clear Args/Returns sections, and a list of common failure modes. Every sentence adds value without redundancy.

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 covers purpose, usage, parameters, return format, and common errors. It is fully adequate for the tool's complexity and context signals.

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?

Only 50% of schema parameters have descriptions, but the description adds clear semantics for both parameters: 'override_endpoint' is an optional public HTTPS URL, and 'oa' is an optional OA ID, effectively compensating 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?

The description specifies a clear verb ('Ping') and resource ('OA's webhook URL'), and distinguishes from sibling tools like 'line_set_webhook_endpoint' by focusing on testing rather than configuration.

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 explicitly states when to use the tool ('Use this whenever a bot stops responding before debugging anything else'), providing clear context, though it does not list alternatives or exclusions.

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