Uwear

Update Garment

update_garment

Destructive

Update a garment's metadata or patch its product photos. Send image changes through assets[] with front/back/side/detail roles. Provided front/back assets replace those singleton roles; provided side/detail assets are added. Omitted existing assets are preserved.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Updated garment name
`assets`	No	Asset patch for garment product photos. A provided full front/back/side replaces that unique view; provided detail assets are added. Omitted existing assets are preserved.
`gender`	No	Updated target gender: male, female, or unisex
`category`	No	Updated canonical garment category
`description`	No	Updated item-level garment description, or a hint to use when patching images
`image_file_1`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_2`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_3`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_4`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_5`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_6`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_7`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_8`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_9`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_10`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_11`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_12`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_13`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_14`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_15`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_16`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_17`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_18`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_19`	No	Generic top-level MCP file object for assets[].image_file references
`image_file_20`	No	Generic top-level MCP file object for assets[].image_file references
`clothing_item_id`	Yes	The garment ID to update

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

addedInput schema / properties / category / enum

Added value: +[
+  "activewear",
+  "baby_and_childrens_clothing",
+  "blouses",
+  "bodysuits",
+  "cardigans",
+  "corset_tops",
+  "hoodies",
+  "overshirts",
+  "polos",
+  "shirts",
+  "sweaters",
+  "sweatshirts",
+  "t_shirts",
+  "tank_tops",
+  "tunics",
+  "dresses",
+  "lingerie",
+  "maternity_clothing",
+  "mens_undergarments",
+  "one_pieces",
+  "outerwear",
+  "outfit_sets",
+  "pants",
+  "shorts",
+  "skirts",
+  "skorts",
+  "sleepwear_and_loungewear",
+  "socks",
+  "suits",
+  "swimwear",
+  "traditional_and_ceremonial_clothing",
+  "uniforms_and_workwear",
+  "wedding_and_bridal_party_dresses",
+  "clothing_accessories",
+  "costumes_and_accessories",
+  "handbag_and_wallet_accessories",
+  "handbags_wallets_and_cases",
+  "jewelry",
+  "shoe_accessories",
+  "shoes",
+  "other"
+]

Changed1 schema field changedAug 29, 2026

addedInput schema / properties / category

Added value: +{
+  "default": null,
+  "description": "Updated canonical garment category",
+  "type": "string"
+}

Changed41 schema fields changedAug 4, 2026
- addedInput schema / $defs / OpenAIFile
```
Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "download_url": {
+      "type": "string"
+    },
+    "file_id": {
+      "type": "string"
+    },
+    "file_name": {
+      "type": "string"
+    },
+    "mime_type": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "download_url",
+    "file_id"
+  ],
+  "type": "object"
+}
```
- addedInput schema / properties / image_file_1 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_1 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_10 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_10 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_11 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_11 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_12 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_12 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_13 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_13 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_14 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_14 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_15 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_15 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_16 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_16 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_17 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_17 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_18 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_18 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_19 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_19 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_2 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_2 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_20 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_20 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_3 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_3 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_4 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_4 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_5 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_5 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_6 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_6 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_7 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_7 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_8 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_8 / default
```
Removed value: -null
```
- addedInput schema / properties / image_file_9 / $ref
```
Added value: +"#/$defs/OpenAIFile"
```
- removedInput schema / properties / image_file_9 / default
```
Removed value: -null
```
First observedAug 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already indicate a destructive, non-read-only operation. The description adds valuable behavioral details: front/back assets replace singleton roles, side/detail assets are added, and omitted assets are preserved. This goes beyond the annotations and clarifies mutation semantics.

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 two sentences, front-loaded with the main purpose, and each sentence carries meaningful information without fluff. No redundant or vague language.

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 complex tool with 26 parameters, the description covers the core actions and asset semantics. It does not explain how to choose between asset_url and image_file, but that is in the schema. No output schema means return value explanation is unnecessary. Overall it is complete enough for correct invocation.

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 coverage is 100%, so each parameter is described. The description adds minor value for assets[] by explicitly stating role behavior, but this largely mirrors the schema's assets description (which already says front/back replace, detail added, omitted preserved). No significant extra meaning is added beyond the schema.

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 clearly states the tool updates a garment's metadata or patches its product photos, using a specific verb and resource. It also explains the asset roles (front/back/side/detail) which distinguishes it from simple create/upload tools. It does not explicitly name alternatives, but the action is clear enough to infer it operates on existing garments.

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 implies usage when updating an existing garment, but does not provide explicit guidance on when not to use it or point to alternatives like upload_garment_from_*. It lacks exclusions or explicit context-setting for sibling tools.

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

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

Resources

Need Help?