Skip to main content
Glama
Degree-AS
by Degree-AS

dw_product_update

Update an existing DynamicWeb product by providing its ID and specifying which fields, custom fields, or category fields to change.

Instructions

Update fields on an existing DynamicWeb product. Fetches the current product, overlays your field updates, and saves via ProductSave (update mode, Query.Type=ProductById).

  • 'fields': top-level product fields (Name, DefaultPrice, Stock, Active, etc.) - PascalCase or camelCase.

  • 'customFields': global product custom fields, keyed by SystemName (e.g. {Color: "red"}).

  • 'categoryFields': product category fields, keyed by SystemName.

Manage the schema of customFields/categoryFields via dw_product_field_save / dw_product_category_save.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProduct ID, e.g. 'PROD1'
languageIdNoLANG1
variantIdNo
fieldsNoTop-level fields, e.g. {DefaultPrice: 99.99, Stock: 42}
customFieldsNoCustom field values keyed by SystemName, e.g. {Color: 'red', BatteryLife: 8}
categoryFieldsNoCategory field values keyed by SystemName
runUpdateIndexNo
Behavior4/5

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

No annotations are present, so the description carries the full burden. It transparently describes the update process (fetch, overlay, save), input field casing conventions, and custom field keying. It lacks details on authentication or error behavior, but is adequate.

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 concise, front-loaded, and contains no extraneous information. It uses clear bullet points for parameter groups. Could be slightly more structured but is effective.

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 moderate complexity with 7 parameters and no output schema, the description provides sufficient behavioral context. It explains the update mechanism and schema management. Missing error handling details, but adequate for most use cases.

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 57% (4 of 7 parameters have descriptions). The description adds meaningful context by explaining the roles of fields, customFields, and categoryFields with examples, compensating for the lower coverage.

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 it updates an existing DynamicWeb product, outlines the process (fetch, overlay, save), and distinguishes its purpose from sibling tools like dw_product_get and dw_product_field_save. The verb and resource are specific.

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

Usage Guidelines4/5

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

The description explains when to use this tool (update product fields) and mentions managing schema via dw_product_field_save / dw_product_category_save as alternatives. However, it does not explicitly state when not to use this tool compared to other update tools.

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/Degree-AS/degree-dynamicweb-mcp'

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