Skip to main content
Glama
hostinger

hostinger-api-mcp

Official
by hostinger

ecommerce_createAProductVariantV1

Add a product variant by specifying option values (e.g., size, color) and price. Automatically creates missing options and returns the new variant.

Instructions

Add a variant to a product along one or more option dimensions (e.g. Size, Color). Options missing from the product are created automatically; provide a value for every option the product already has. Prices are integers in the smallest currency unit and default to the store currency. Returns the created variant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuNoThe variant SKU.
titleNoThe variant title. Defaults to the option values joined with ' / ' (e.g. 'Red / L').
pricesNoPrices per currency. Amounts are integers in the smallest currency unit. A free item is amount: 0.
optionsYesOption name/value pairs that distinguish this variant, e.g. [{name: Size, value: M}]. Options missing from the product are created; provide a value for every option the product already has.
store_idYesThe ID of the store that owns the product.
product_idYesThe ID of the product to add the variant to.
manage_inventoryNoWhether stock is tracked for this variant. Defaults to false.
inventory_quantityNoUnits in stock. Defaults to 0.
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the auto-creation of missing options, integer/minor-currency-unit pricing, the store-currency default, and that the created variant is returned. These are meaningful side effects and defaults beyond what the schema states, though it does not cover error or conflict behavior.

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

Conciseness5/5

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

Three focused sentences with no filler or repetition. The action is front-loaded, followed by the most important behavioral rule and then pricing/return details. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete enough for an agent to invoke the tool correctly: it covers the core option semantics, price units/defaults, and the return value. The schema fully documents all 8 parameters. Missing details around duplicate handling and permissions are not critical for a straightforward creation tool.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds real value by explaining the `options` contract (auto-create vs. must-provide existing options) and clarifying `prices` are integers in the smallest currency unit defaulting to store currency. That goes beyond the schema's individual parameter descriptions.

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 opens with a specific verb and resource: 'Add a variant to a product', which clearly identifies the operation. It also narrows the scope to 'one or more option dimensions (e.g. Size, Color)'. It does not explicitly name sibling variant tools, but the action is distinct enough from list/update/delete variant tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context about how options behave ('Options missing from the product are created automatically; provide a value for every option the product already has') but does not offer explicit when-to-use guidance or alternatives. It does not mention that batch variant creation exists as a sibling, so an agent gets no routing help.

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/hostinger/api-mcp-server'

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