Skip to main content
Glama
woraphol-j

LINE Shopping API MCP

by woraphol-j

Mark_as_ship

Mark order as shipped with tracking number to update status to complete.

Instructions

Update order status to Complete by Mark shipment status as shipped and add tracking number

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderNoYesOrder number
trackingNumberNo
trackingUrlNo

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?

With no annotations, the description bears full responsibility for behavioral disclosure. It states the action but omits any side effects, reversibility, error cases, or permission requirements. This is minimal for a status-changing tool.

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

Conciseness4/5

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

The description is a single sentence, front-loading the primary action. It is concise with no wasted words.

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?

Despite having an output schema, the description lacks sufficient context for a tool with three parameters and sibling tools. It does not explain optionality of trackingNumber and trackingUrl, nor does it highlight any constraints. An agent may misinterpret required vs optional fields.

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

Parameters2/5

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

Schema description coverage is only 33% (one of three parameters has a description). The description adds 'add tracking number' but does not clarify which parameter corresponds to that, nor does it explain trackingUrl's role or optionality. The meaning is not significantly enhanced beyond the schema.

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 clearly states the tool updates order status to Complete by marking shipment as shipped and adding a tracking number. It is specific about verb and resource, but does not explicitly distinguish from sibling tools like Update_tracking_number or Mark_as_paid_COD, which have similar scopes.

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. There is no mention of prerequisites or exclusions, leaving the agent without context for selection.

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