Skip to main content
Glama
runnel

voog-mcp

by runnel
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

product_update

Idempotent

Update a product's attributes, translations, or legacy fields. Validates input and supports reversal.

Instructions

Update a product. Three argument shapes (combinable):

  • attributes: flat object of root-level product fields (status, price, sale_price, sku, stock, description, category_ids, image_id, asset_ids, physical_properties, uses_variants, variant_types, variants, variant_attributes). Note: asset_ids accepted; on PUT it's translated to the assets:[{id}] envelope Voog requires (sending raw asset_ids on PUT silently keeps only the hero image). variants without variant_attributes wipes ALL variants (even ones with id); pass both together, or set force=true to acknowledge.

  • translations: nested {field: {lang: value}} for translatable fields (name, slug, description). Each field-language pair must be non-empty. Cannot overlap with attributes (e.g. attributes.description + translations.description in the same call is rejected).

  • fields (legacy v1.1 shape): flat 'name-et', 'slug-en' keys — auto-routed to translations. Kept for back-compat. At least one of attributes/translations/fields must be non-empty. Validates status enum {'draft', 'live'} and rejects unknown attribute keys (catches typos before they round-trip to a 422). Reversible by calling with previous values; idempotent (same input twice = same end state).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYes
product_idYes
attributesNoRoot-level product fields. Allowed keys: status, price, sale_price, sku, stock, description, category_ids, image_id, asset_ids, physical_properties, uses_variants, variant_types, variants, variant_attributes. asset_ids accepted; on PUT it's translated to the `assets:[{id}]` envelope Voog requires.
translationsNoNested {field: {lang: value}}. Allowed fields: name, slug, description.
fieldsNoLegacy v1.1 shape: flat 'name-et', 'slug-en' keys. Auto-routed to translations.
forceNoRequired to send `variants` without `variant_attributes` — Voog wipes all variants in that case. Default false.

Tool Definition Quality

A4.3/5.0
Behavior5/5

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

The description discloses key behaviors beyond annotations: asset_ids translation, variant wiping with force flag, validation of status enum and unknown keys, reversibility, and idempotency. This provides rich context for safe invocation.

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 bullet points and front-loaded key info, but it is somewhat verbose. Every sentence adds value, though it could be more concise.

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?

Given the complexity (6 parameters, nested objects, no output schema), the description covers most aspects: argument shapes, constraints, validations, idempotency, and reversibility. It lacks explicit mention of return value or permissions, but is largely complete.

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?

The description adds meaning beyond the input schema, such as the combinability of argument shapes, the non-overlap rule between attributes and translations, and the legacy fields routing. The schema already covers some details, but the description clarifies edge cases.

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 'Update a product' and details three argument shapes, making the verb and resource specific. It distinguishes itself from siblings like product_create, product_delete, etc., by focusing on updating an existing product.

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 explains how to use the tool, including combinable shapes and constraints, but does not explicitly guide when to use this tool over alternatives like product_set_images. It implies usage context but lacks explicit exclusions or comparisons.

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