Skip to main content
Glama
Sign In
apparelhub-mcp

apparelhub-mcp

Official
by ApparelHub-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

submit_order_to_fulfillment

Idempotent

Manually submits an order to Printful/Printify as a draft, auto-fetching recipient for sales-channel orders. Use to un-stick paid orders that never got submitted, then confirm if needed.

Instructions

Manually submit an order to its fulfillment provider (Printful/Printify) as a DRAFT. For sales-channel orders this auto-fetches the recipient from the channel. Use to un-stick a paid order that never got submitted; confirm it afterward with confirm_order if the store requires confirmation.

[#437d68]

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": {
      "order_uuid": "<order_uuid>"
    },
    "name": "submit_order_to_fulfillment"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoWorkspace uuid to scope to (agency accounts). Omit for Default.
order_uuidYesThe order uuid (from list_my_orders / get_order_details).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.15.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare openWorldHint and idempotentHint, leaving side-effect disclosure to the description, which does deliver: the submission lands as a DRAFT at an external provider, sales-channel orders auto-fetch the recipient, and some stores require a confirming call afterwards. It does not say whether a submission can be retracted or what the provider returns, which keeps it from a 5.

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?

Two front-loaded sentences with the action and its draft nature stated first, then the use case and follow-up. The trailing token '[#437d68]' is unexplained noise that costs a point.

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 non-output-schema mutation tool with complete schema coverage, the description supplies everything an agent needs: the manual trigger, the draft semantics, the auto-fetch behavior, and the confirm_order follow-up.

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?

With 100% schema description coverage on only two parameters, the schema already explains workspace scoping and the order_uuid source (list_my_orders / get_order_details). The description adds no parameter-level detail, so the baseline of 3 is appropriate.

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?

Specific verb (submit) + resource (order) + destination (fulfillment provider, naming Printful/Printify) + scope (as a DRAFT). The word 'Manually' immediately separates it from the automated sync_to_fulfillment sibling, so an agent can route without opening either schema.

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?

Gives a clear triggering condition ('un-stick a paid order that never got submitted') and names confirm_order as a required follow-up when the store requires confirmation. It stops short of stating when NOT to use it (e.g. when sync_to_fulfillment is the right path for non-stuck orders), so it is strong but not fully explicit about the alternative.

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