Skip to main content
Glama
Sign In
apparelhub-mcp

apparelhub-mcp

Official
by ApparelHub-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_store_settings

Idempotent

Update a store's fulfillment workflow and notification settings, including automation mode, approval authority, and order-hold guardrails, while changing only the fields you pass.

Instructions

Update a store's fulfillment workflow / notification settings. Only the fields you pass are changed. fulfillment_mode: "auto" (auto-pilot: paid -> draft -> auto-confirm -> production), "confirm" (auto-draft, you confirm each order), "review" (held before submission for approval). The hold_* guardrails escalate an otherwise-auto/confirm order to a pre-submission review. Set hold_orders_above_amount / hold_below_margin_pct to null to disable that guardrail. hold_channel_risk_review is ON by default and OVERRIDES fulfillment_mode (including "auto"): an order the sales channel is reviewing is never sent to fulfillment while it may still be voided.

[#095099]

Input Schema

NameRequiredDescriptionDefault
workspaceNoWorkspace uuid to scope to (agency accounts). Omit for the Default workspace.
store_uuidYesThe store uuid to update.
fulfillment_modeNoAutomation level: auto (auto-pilot), confirm (you confirm each), review (approve before submit).
approval_authorityNoWho decides when a review is required: human (UI queue), agent (API/callback), rules (auto unless a guardrail trips).
notify_on_shipmentNoSend a notification when an order ships.
notify_on_new_orderNoSend a notification when a new order arrives.
auto_reconcile_ordersNoPeriodically re-sync open sales-channel orders with their channel (manual reconcile always works regardless).
hold_below_margin_pctNoAuto-hold orders below this profit-margin percent. null disables the guardrail.
auto_fulfill_on_paymentNoAuto-submit to the provider once payment clears.
hold_on_negative_marginNoAuto-hold orders that would lose money.
hold_channel_risk_reviewNoON by default. Hold an order the SALES CHANNEL has flagged as under its own risk review, so it is never sent to fulfillment while the channel may still void it. Unlike the other guardrails this one OVERRIDES fulfillment_mode, including "auto". Turning it off restores the chosen workflow for those orders.
hold_first_time_customerNoAuto-hold the first order from a new customer.
hold_orders_above_amountNoAuto-hold orders whose total exceeds this amount. null disables the guardrail.
notify_on_tracked_ordersNoAlso notify about orders for the merchant's own products (not made in ApparelHub, fulfilled by their store). Off by default; the orders are recorded either way.
require_payment_before_fulfillNoBlock fulfillment until the order is paid.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.19.0
    • addedInput schema / properties / notify_on_tracked_orders
      Added value: +{
+  "description": "Also notify about orders for the merchant's own products (not made in ApparelHub, fulfilled by their store). Off by default; the orders are recorded either way.",
+  "type": "boolean"
+}
  2. First observedv0.15.2

TDQS

A4.1/5.0
Behavior4/5

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

The description adds meaningful behavior beyond the annotations: only passed fields are changed, null disables certain guardrails, and hold_channel_risk_review is ON by default and overrides fulfillment_mode. This is strong disclosure for a mutation tool, though it does not cover authorization requirements or response behavior.

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 description is front-loaded with the core action and every substantive sentence explains setting behavior rather than repeating the schema. It is dense for a 15-parameter tool, and the trailing '[#095099]' artifact is unexplained noise.

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?

Given the tool's complexity, the description covers the important non-obvious semantics: partial updates, guardrail defaults, override behavior, and disabling thresholds. There is no output schema, and the description does not discuss return behavior or permissions, but it is complete enough for correct invocation of the main settings.

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 already 100%, so the schema carries most parameter documentation. The description still adds useful interpretation: fulfillment_mode sequences, guardrail escalation behavior, and how to disable amount and margin holds with null.

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 states a specific verb and resource: update a store's fulfillment workflow and notification settings. It distinguishes this from store-reading tools like get_store_settings and from channel-specific settings by explicitly naming the scope as fulfillment workflow / notification settings.

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?

Usage is implied by the name and the explanation of settings, but the description does not explicitly say when to use this instead of get_store_settings, set_channel_settings, or other store-management tools. It also does not mention prerequisites such as reading current settings first.

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