Skip to main content
Glama

product_create

Create a product by providing name, slug, and price. Optionally add attributes, translations, or legacy fields. Returns the new product ID.

Instructions

Create a new product (POST /products on ecommerce v1). Required: name, slug, price (Voog rejects POST without these). Three argument shapes (combinable):

  • attributes: flat object of root-level product fields. Allowed keys: name, slug, price, sale_price, status, description, sku, stock, reserved_quantity, category_ids, image_id, asset_ids, physical_properties, uses_variants, variant_types. Note: POST uses asset_ids (list of int), unlike PUT which uses assets:[{id}].

  • translations: nested {field: {lang: value}} for translatable fields (name, slug, description). Each field-language pair must be non-empty.

  • fields (legacy v1.1 shape): flat 'name-et', 'slug-en' keys — auto-routed to translations. Validates status enum {'draft', 'live'} and rejects unknown attribute keys. The POST result includes the newly assigned product id. Price fields (price, sale_price, effective_price) are net or gross depending on settings.price_entry_mode. Call ecommerce_settings_get to determine the mode. For customer-facing pricing always use effective_price and verify the mode first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYes
attributesNoRoot-level product fields. Required (in this or in `translations`/`fields`): name, slug, price.
translationsNoNested {field: {lang: value}}. Allowed fields: name, slug, description.
fieldsNoLegacy v1.1 shape: 'name-et', 'slug-en' keys. Auto-routed to translations.
Behavior5/5

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

The description discloses many behavioral details beyond annotations, such as required fields, validation of status enum, rejection of unknown keys, difference between POST and PUT, and dependency on price entry mode settings. Annotations are minimal, so the description carries the full burden well.

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 well-structured with a main purpose sentence followed by details. It could be slightly trimmed but remains clear and informative for a complex tool.

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 covers required fields, validation, argument shapes, and hints at results (new product id). It does not include error handling details or full return structure, but is adequate for an agent to use correctly.

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

Parameters5/5

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

The description adds significant meaning beyond the input schema by explaining the three argument shapes, allowed keys, combinations, and legacy format. Even with 75% schema coverage, it enriches understanding.

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

Purpose5/5

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

The description clearly states 'Create a new product (POST /products on ecommerce v1).' It specifies the verb and resource, and distinguishes from related tools like product_update by focusing on creation.

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 does not explicitly compare with sibling tools like product_update or product_duplicate, but it implies usage for creating new products. It provides guidance on required fields and argument shapes, which helps in correct usage.

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/runnel/voog-mcp'

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