Skip to main content
Glama
woraphol-j

LINE Shopping API MCP

by woraphol-j

Update_product_detail

Update product details including name, brand, category, description, images, licenses, and variant options by providing the product ID.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProduct id
brandNoProduct brand
categoryIdNoProduct category id
codeNoProduct code
descriptionNoProduct description with HTML formatting support
imageUrlsNoProduct image urls
licensesNoThe list of licenses for your product.
nameNoProduct name
variantOptionsNoProduct variant options

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?

With no annotations, the description must disclose behavioral traits. It only says 'updating' without mentioning side effects, authorization, rate limits, or failure handling. The link for category ID is helpful but insufficient for a mutation 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 very short (two sentences), with no fluff. However, it could be more informative without adding length. Conciseness is good, but lacks depth.

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 (9 parameters, nested objects, output schema exists), the description is too minimal. It does not explain prerequisites, overall effect, or how it differs from sibling tools. The output schema covers return values, but the description should provide more context.

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%, so the schema already describes all parameters. The description adds a link for the category ID parameter but does not provide further semantic value beyond the schema. Baseline of 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 states it is for 'product detail updating,' which is clear about the verb and resource. However, it does not explicitly differentiate from sibling tools like Update_product_price or Update_product_variant_detail, though the name implies a broader 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?

The description offers no guidance on when to use this tool versus alternatives. Given sibling tools for specific updates (price, variant, display status), the lack of context on when to choose this generic update tool is a gap.

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