Skip to main content
Glama
wasintoh

line-oa-mcp-ultimate

by wasintoh

Set LINE Webhook Endpoint

line_set_webhook_endpoint
Idempotent

Set or get the webhook URL for your LINE Official Account to receive events. Use with line_test_webhook for verification.

Instructions

Read or write the LINE OA's webhook URL (PUT/GET /v2/bot/channel/webhook/endpoint). Complements line_test_webhook — set the URL here, then ping it with line_test_webhook.

Args:

  • mode ('set' | 'get'): write or read.

  • endpoint (string, set only): public HTTPS URL (https:// required, ≤500 chars).

  • oa (string, optional): OA id. Default = active OA.

Returns: { endpoint: string, active: boolean } // re-read after a 'set' to confirm

Examples:

Errors:

  • Non-HTTPS or >500 char URL → inline input error (LINE requires HTTPS).

  • mode='set' without endpoint → inline input error.

  • LINE rejects the URL → LineApiError surfaced.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesset: write a new webhook URL; get: read the currently configured one.
endpointNoRequired for mode='set'. Public HTTPS URL (must start with https://, ≤500 chars).
oaNoOptional OA id; defaults to active OA.
Behavior5/5

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

The description clearly states that setting a webhook returns a re-read confirmation with endpoint and active status, and lists error scenarios (non-HTTPS, no endpoint with set, LINE rejection). This adds context beyond the annotations (which indicate idempotency but don't detail return behavior).

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 for description, args, returns, examples, and errors. Every sentence adds value, no fluff. Front-loaded with purpose and sibling relation.

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?

For a tool with 3 parameters and no output schema, the description provides complete coverage: input semantics, return structure, error handling, examples, and relation to sibling tools. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains the 'mode' parameter's two values, the 'endpoint' constraints (HTTPS required, ≤500 chars), and the fallback for 'oa'. Examples illustrate valid combinations. Schema coverage is 100%, but the description adds practical usage context and error handling info.

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 the purpose: 'Read or write the LINE OA's webhook URL' with the specific HTTP methods. It distinguishes itself from the sibling tool 'line_test_webhook' by explaining the complementary workflow.

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 explains when to use this tool ('set the URL here, then ping it with line_test_webhook') and provides default behavior for the 'oa' parameter. Error conditions and examples offer clear guidance.

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