Skip to main content
Glama
woraphol-j

LINE Shopping API MCP

by woraphol-j

Order_detail

Retrieve order details using an order number. Access specific information about a LINE Shopping order.

Instructions

An API for getting an order detail

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNoYesOrder number

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkoutAtNoCheckouted date
discountAmountNoTotal discount from the order price (excluding instant discounts applied to products)
isGiftNoIf product is set to 'Allow gift' or 'Gift only' will be returned 'true'
lastUpdatedAtNoLast updated date
orderItemsNo
orderNumberNoOrder number
orderStatusNoOrder status
paidAtNoPaid date
paymentMethodNoPayment method
paymentStatusNoPayment status
remarkBuyerNoNote from buyer
remarkRecipientNoRemark recipient
shipmentDetailNo
shipmentPriceNoTotal shipping fee
shipmentStatusNoShipment status
shippingAddressNo
subtotalPriceNoSubtotal price after applying instant discount to order items
totalPriceNoTotal order price (subtotalPrice + shipmentPrice - discountAmount)
weightNoTotal weight
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only states 'getting' which implies a read operation, but does not disclose permissions, rate limits, or response format. The description carries the full burden and is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is very concise (6 words), but is under-specified. It is not padded with fluff, but the brevity reduces informativeness. An ideal concise description would be a bit more specific.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (1 parameter, output schema present), the description barely meets minimum completeness. It fails to explain what constitutes an 'order detail' or any constraints, relying entirely on the output schema.

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

Parameters3/5

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

Schema coverage is 100% with a single parameter 'orderNo' described as 'Order number'. The description adds 'order detail' context but does not improve upon the schema's existing documentation. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'An API for getting an order detail' clearly states the verb (getting) and resource (order detail). It distinguishes from sibling tools like 'Get_all_orders' by implying a single-order query, but does not explicitly differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as 'Get_all_orders' or 'Settlement_detail'. No prerequisites or context for invocation.

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/woraphol-j/lineshopping-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server