Skip to main content
Glama
woraphol-j

LINE Shopping API MCP

by woraphol-j

Get_all_orders

Retrieve orders filtered by search, status, payment, shipment, order type, date range, with pagination and sorting options.

Instructions

An API for getting a list of orders by condition

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoFor searching the 'customer name' or 'order number' that partial match the given keyword
pageNoFor pagination, page is the page number to query the list of orders
perPageNoFor pagination, per page is the number of showing orders on a page
sortByNoFor sorting of results by specific field
orderByNoTo define whether results are sorted in ascending or descending order
orderStatusNoFiltered by multiple values of order status
paymentStatusNoFiltered by multiple values of payment status
paymentMethodNoFiltered by multiple values of payment method
shipmentStatusNoFiltered by multiple values of shipment status
orderTypeNoFiltered by multiple values of order type
startAtNoFiltered by starting point of updated time. Example value is '2022-01-01T09:30:00Z'
endAtNoFiltered by ending point of updated time. Example value is '2022-01-01T09:30:00Z'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
currentPageNoCurrent page number
dataNo
perPageNoNumber of showing orders per page
totalPageNoTotal page numbers of the result
totalRowNoTotal number of orders
Behavior2/5

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

With no annotations, the description fails to disclose any behavioral traits such as pagination behavior, result limits, or side effects. It only states the basic purpose, leaving the agent uninformed about important runtime characteristics.

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 a single sentence, which is concise, but it lacks structure and does not front-load the most critical information. It is minimal but not wasteful, earning a middle score.

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 tool has 12 parameters, no annotations, and an output schema (not shown), the description is insufficient. It does not mention pagination, sorting, default ordering, or what happens when no parameters are provided. The agent needs more context to use this tool correctly.

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?

The input schema has 100% description coverage, so all parameters are already documented in the schema. The description adds no additional meaning beyond 'by condition', which is already implied by the many filter parameters. Thus, the description does not enhance parameter understanding.

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 states it gets a list of orders by condition, which clearly indicates the tool's function of retrieving filtered order lists. However, it does not specify that the list supports pagination, sorting, and multiple filter parameters, which are evident from the schema but not mentioned in the description.

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 is provided on when to use this tool versus alternatives like Order_detail (which retrieves a single order) or other list tools. The description lacks any context about prerequisites, typical use cases, 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/woraphol-j/lineshopping-api-mcp'

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