Skip to main content
Glama

mu

by com.wearmu

Update an MU product

mu_update_product

Update one of your products. Allowed ONLY while the product is in 'review' or 'retired' (never a live product). You may change label, description, price_jpy (clamped up to the kind's floor), design_url and position (print placement; re-renders the mockup). Printful ids can never change. Owner-only. Requires Authorization: Bearer <api_key>.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuYesSKU of the product to update (must belong to one of your stores).
labelNoNew product label / title.
positionNoOptional print placement — front-print DTG apparel only (tee / tee_white / hoodie / crewneck / tank / long_sleeve_tee). The preview mockup AND the real print order use the same resolved box (WYSIWYG). Preview with mu_preview_mockup before creating.
price_jpyNoNew retail price in JPY (clamped up to the kind's price_floor_jpy).
design_urlNoNew absolute https URL to the design artwork.
descriptionNoNew product description.

TDQS

A4.6/5.0
Behavior5/5

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

Given no annotations, the description fully informs about behaviors: price clamping, position triggering re-render, immutable Printful IDs, owner-only access, and auth requirement. Also warns that mockup preview should be used before applying position changes.

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?

Single paragraph, front-loaded with the core action, then efficiently lists constraints and fields. Every sentence adds important information without redundancy.

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?

Covers all key aspects: allowed states, modifiable fields, constraints, auth, and refers to preview mockup tool. No output schema, but return values are not critical. Minor confusion with 'before creating' instead of 'before updating' but still adequate.

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 has 100% description coverage, so baseline is 3. The description adds value by explaining price clamping ('clamped up to the kind's floor'), position triggering re-render, and that design_url must be absolute https. These details go beyond schema.

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 'Update one of your products' and specifies the allowed states ('review' or 'retired'), distinguishing it from create and retire tools. It lists the updatable fields, making the purpose unambiguous.

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?

Explicitly says 'Allowed ONLY while the product is in review or retired' and 'Owner-only. Requires Authorization: Bearer <api_key>.' Implicitly indicates when not to use (not on live products) but does not explicitly name alternatives.

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

All mu toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose; no two tools appear to do the same thing. Even closely related tools (e.g., mu_quote vs mu_rfq_create, mu_preview_mockup vs mu_create_product) are differentiated by read-only vs. action, or draft vs. send.

Naming Consistency5/5

Tool names consistently use snake_case with the mu_ prefix, and follow a clear verb_noun or noun_verb pattern. Groups like mu_gi_*, mu_ship_*, mu_rfq_* maintain internal consistency. No arbitrary or ambiguous names.

Tool Count4/5

The tool count of 28 is on the higher side but appropriate for the breadth of functionality (registration, product lifecycle, manufacturing, shipping, sales, admin). It's well within a manageable range for a comprehensive server.

Completeness4/5

The tool surface covers core workflows comprehensively: registration, product CRUD (with create, update, retire), manufacturing quotes (informational and RFQ with spec drafting), shipping (CSV, tracking, status updates), sales data, and gi-specific management. Minor gaps include lack of store update/delete and product search, but these are not critical for the main use cases.

Resources