3Dsellers

update-product

Destructive

Fully update an existing product (PUT). Replaces all fields including variants, warehouse quantities and custom attributes. Product data this API does not expose, and package / seoKeywords when omitted, keep their stored values. Authenticated via bearer token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "productId": "<productId>",
      "product": "<product>"
    },
    "name": "update-product"
  }
}

Input Schema

Name	Required	Description	Default
`product`	Yes
`productId`	Yes	Product ID to update

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 3, 2026

changedInput schema / properties / product / properties / categoryId / description

Previous value: -"Category ID"New value: +"Catalog category ID (get-product-categories). Optional: on create, leave it out when the seller named none — the product is created without a category (null) and can be categorised later; on update or patch, leaving it out keeps the stored one. Do not pick or create one on your own."

addedInput schema / properties / product / properties / price / properties / currency / description
```
Added value: +"Currency code, e.g. USD"
```
addedInput schema / properties / product / properties / price / properties / msrp / description
```
Added value: +"Manufacturer suggested retail price. Optional — omit when unknown."
```
addedInput schema / properties / product / properties / price / properties / price / description
```
Added value: +"Selling price"
```
addedInput schema / properties / product / properties / price / properties / wholesalePrice / description
```
Added value: +"Wholesale / cost price. Optional — omit when the seller gave none, never guess it."
```

changedInput schema / properties / product / properties / price / required

Previous value: -[
-  "price",
-  "currency",
-  "wholesalePrice",
-  "msrp"
-]New value: +[
+  "price",
+  "currency"
+]

removedInput schema / properties / product / required
```
Removed value: -[
-  "categoryId"
-]
```

First observedOct 26, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description discloses the key behavioral traits: it replaces all fields including variants and warehouse quantities, and that data the API does not expose plus omitted `package`/`seoKeywords` retain stored values. It also states the bearer-token auth requirement. This is exactly the context an agent needs before a destructive write.

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?

Four short sentences, front-loaded with the operation and its replacement semantics before the preservation caveats and auth note. No filler, and each sentence carries distinct information.

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?

For a deeply nested, 50%-documented payload with no output schema, the description covers the essential risk profile: full replacement, what is preserved, and auth. The main residual gap is the exact consequence of omitting sub-collections like `variants` or `customAttributes`, which an agent must know before invoking a destructive replace.

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 description coverage is around 50% and the schema itself already documents `package`, `seoKeywords`, `categoryId` and variant SKU matching semantics. The description adds the important top-level replace-vs-preserve rule for the whole `product` object, but does not clarify ambiguous cases such as whether an omitted `variants` array deletes existing variants.

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 gives a specific verb and resource ('Fully update an existing product (PUT)') and immediately states the replacement scope. It signals full-replacement semantics that distinguish it from a partial-update sibling, but it never names `patch-product` explicitly, so the distinction is inferred rather than stated.

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 parenthetical '(PUT)' and 'Replaces all fields' imply the full-replacement use case, so an agent can infer when this is appropriate versus a partial update. However, there is no explicit instruction such as 'use patch-product when updating only a few fields', and no prerequisites or preconditions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 3Dsellers tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.