swop

Update or unlist a product

swop_update_product

Destructive

Edit one of the linked account's products, or unlist it. Pass its productId (from swop_list_my_products) plus ONLY the fields to change — anything omitted keeps its current value. To unlist it, set status to 'archived'. Confirm price and name changes with the user first.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New product name
`image`	No	New primary image URL
`status`	No	Set 'archived' to unlist
`keywords`	No	Replaces the keywords
`priceUsd`	No	New price in USD (settles in USDC)
`variants`	No	Buyer-selectable options. Replaces the existing set when given.
`mintLimit`	No	New inventory available
`productId`	Yes	The product id from swop_list_my_products
`description`	No	New description
`extraImages`	No	Replaces the additional images. Requires image, since the full list is rewritten
`shippingCost`	No	Flat shipping cost in USD
`requiresShipping`	No	Collect a shipping address
`royaltyRecipient`	No	Wallet receiving royalties
`royaltyPercentage`	No	Resale royalty percent
`digitalDeliveryNote`	No	What a buyer receives

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 16, 2026

addedInput schema / properties / digitalDeliveryNote

Added value: +{
+  "description": "What a buyer receives",
+  "maxLength": 500,
+  "type": "string"
+}

addedInput schema / properties / extraImages

Added value: +{
+  "description": "Replaces the additional images. Requires image, since the full list is rewritten",
+  "items": {
+    "format": "uri",
+    "type": "string"
+  },
+  "maxItems": 9,
+  "type": "array"
+}

changedInput schema / properties / image / description

Previous value: -"New product image URL"New value: +"New primary image URL"

addedInput schema / properties / keywords

Added value: +{
+  "description": "Replaces the keywords",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

changedInput schema / properties / mintLimit / description

Previous value: -"New inventory limit"New value: +"New inventory available"

addedInput schema / properties / requiresShipping

Added value: +{
+  "description": "Collect a shipping address",
+  "type": "boolean"
+}

addedInput schema / properties / royaltyPercentage

Added value: +{
+  "description": "Resale royalty percent",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / royaltyRecipient

Added value: +{
+  "description": "Wallet receiving royalties",
+  "type": "string"
+}

addedInput schema / properties / shippingCost

Added value: +{
+  "description": "Flat shipping cost in USD",
+  "minimum": 0,
+  "type": "number"
+}

changedInput schema / properties / status / description

Previous value: -"Set 'archived' to unlist the product"New value: +"Set 'archived' to unlist"

addedInput schema / properties / variants

Added value: +{
+  "description": "Buyer-selectable options. Replaces the existing set when given.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "description": "Variant group, e.g. \"Color\" or \"Size\"",
+        "minLength": 1,
+        "type": "string"
+      },
+      "options": {
+        "description": "Choices, e.g. [\"Black\",\"White\"]",
+        "items": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "name",
+      "options"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

AddedSep 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description aligns with those flags. It adds useful behavioral nuance: edits are partial, unlisting is done via status='archived', and user confirmation is required for name/price changes. It does not detail side effects beyond those, but the annotation lowers that burden.

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?

The description is three tight sentences with no filler. It front-loads the core edit/unlist purpose, then gives the essential operational rules, and every sentence contributes a distinct fact an agent needs.

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 15-parameter mutation tool, the description covers the key orchestration rules: partial updates, provenance of productId, unlisting behavior, and confirmation requirements. The schema fully describes each parameter. The only notable gap is the absence of return/error behavior, which matters more because there is no output schema.

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 schema already handles individual parameter meanings. The description adds value with patch semantics ('ONLY the fields to change'), clarifies unlisting through status, and flags name/price changes as requiring user confirmation, which is not apparent from the schema alone.

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 the action ('Edit') and the resource ('one of the linked account's products'), and additionally covers the unlist behavior. This distinguishes it from sibling tools like swop_create_product and swop_list_my_products without relying on the title alone.

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?

It gives concrete usage instructions: pass productId, send only the fields to change, leave omitted fields unchanged, and set status to 'archived' to unlist. It also instructs the agent to confirm price and name changes with the user first. It does not explicitly contrast with create/feature alternatives, so it stops short of a 5.

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

All swop 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.

Update or unlist a product

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources