Skip to main content
Glama
woraphol-j

LINE Shopping API MCP

by woraphol-j

Create_product_variants

Configure product variants by defining options (e.g., color, size) and specifying price, weight, and stock for each.

Instructions

An API for product variants creation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProduct id
variantOptionsYesProduct variant options for designating the variant
variantsYesProduct variant template

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 provided, and the description does not disclose behavioral traits such as whether the operation is destructive, authentication requirements, or side effects like inventory adjustments.

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

Conciseness2/5

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

The description is very short but fails to convey critical information. It is not front-loaded with the most important details, making it less helpful despite its brevity.

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 complexity of the input schema (nested objects, three required parameters), the description is too sparse. It does not reference the output schema or explain the relationship between 'variantOptions' and 'variants'.

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?

The input schema has 100% description coverage for all parameters, but the tool description itself adds no additional meaning or context beyond what the schema already provides.

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

Purpose3/5

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

The description states 'product variants creation', which matches the tool name and distinguishes from 'Create_product' and other sibling tools. However, it is generic and does not specify what constitutes a product variant or that it requires an existing product ID.

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?

There is no guidance on when to use this tool versus alternatives like 'Create_product'. No prerequisites or conditions (e.g., product must exist) are mentioned.

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