Skip to main content
Glama
Sign In
apparelhub-mcp

apparelhub-mcp

Official
by ApparelHub-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

move_product_to_workspace

Transfers a product to another agency workspace by re-stamping its workspace. If a store or orders block it, copy instead; check with check_product_move first.

Instructions

Move a product to another workspace (agency accounts) by re-stamping its workspace. Fails with a 409 (blocking list) if the product is mapped to a store or has orders — copy it instead in that case (check first with check_product_move). Use list_my_workspaces for the destination uuid; pass source_workspace if the product is not in your Default workspace.

[#f36e77]

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": {
      "product_uuid": "<product_uuid>",
      "destination_workspace": "<destination_workspace>"
    },
    "name": "move_product_to_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_uuidYesThe product to transfer.
source_workspaceNoThe workspace the asset currently lives in. Omit only if it is in your Default workspace; otherwise you must pass it (the platform scopes reads to a single workspace).
destination_workspaceYesDestination workspace uuid to copy/move into. Get it from list_my_workspaces (resolve a client/brand name to its uuid).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.15.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only provide openWorldHint=true, so the description carries the burden and does so thoroughly: it discloses the 409 failure mode, the exact blocking conditions (store mapping or existing orders), and the required fallback path. This is rich behavioral context an agent cannot get from structured fields.

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 action, scope, and failure/fallback path are front-loaded and dense with useful constraints. A stray artifact ('[#f36e77]') at the end is noise and slightly detracts.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema, the description supplies everything needed to call it correctly: destination uuid sourcing, source_workspace defaulting, the 409 precondition, and the alternative operation. Nothing essential is missing.

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 100%, so the schema already documents all three parameters including the source_workspace default caveat and destination uuid source. The description reinforces but adds little beyond what the schema states, so baseline 3 applies.

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?

States a precise verb+resource ('Move a product to another workspace') and scopes it to agency accounts. It also implicitly distinguishes itself from check_product_move and copy_product_to_workspace by naming them as the check/fallback tools.

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

Usage Guidelines5/5

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

Explicitly covers when this will fail ('409 if mapped to a store or has orders'), what to do instead ('copy it'), and the prerequisite check ('check first with check_product_move'). It also tells the agent to use list_my_workspaces for the uuid and when to pass source_workspace.

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

Deploy Server

Other Tools