Skip to main content
Glama
woraphol-j

LINE Shopping API MCP

by woraphol-j

Create_product

Create a product on LINE Shopping by specifying category, code, images, name, variant options, and pricing.

Instructions

An API for product creation. For product Categories ID variable please find more information on Development guideline

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandNoProduct brand
categoryIdYesProduct category id
codeYesProduct code
descriptionNoProduct description with HTML formatting support
imageUrlsYesProduct image urls
instantDiscountNoProduct instant discount must be greater than 0. If instant discount amount is 0, the instant discount will be disabled.
licensesNoThe list of licenses for your product
nameYesProduct name
variantOptionsNoProduct variant options
variantsYesProduct variants

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandNoProduct brand
categoryNoCategory Object
codeNoProduct code
descriptionNoProduct description with HTML formatting support
giftGroupsNoGift Groups of product
giftOptionNoProduct Gift Option
hasOnlyDefaultVariantNoIf product doesn't have any variant will be returned 'true'
idNoIdentifying number of product
imageUrlsNoProduct image urls
instantDiscountNoIf product doesn't have instant discount will be returned '0' otherwise returned with number
isDisplayNoIf product is displaying on storefront will be returned 'true'
licensesNoThe list of licenses for your product
nameNoProduct name
variantOptionsNoProduct options such as size or color
variantsNoProduct variants
Behavior2/5

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

No annotations are present, so the description must carry the full burden. It only states 'API for product creation' without mentioning side effects, authentication, rate limits, or other behavioral traits.

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 plus an HTML link, which is concise but lacks structure. It could be more informative without becoming verbose.

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?

For a complex tool with 10 parameters and nested objects, the description is too minimal. It does not provide a high-level overview of what the tool does (e.g., creates a full product with variants) or mention 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?

The input schema has 100% description coverage, so the description adds minimal extra value. The link for categoryId is a small addition, but overall it does not significantly enhance understanding beyond what the schema provides.

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 'API for product creation', which clearly identifies the verb and resource. However, it does not differentiate from sibling tools like 'Create_product_variants', which could lead to confusion about scope.

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 (e.g., updates via 'Update_product_detail'). The description lacks context on prerequisites 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