Skip to main content
Glama
ApparelHub-AI

apparelhub-mcp

Official
by ApparelHub-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

start_channel_connect

Begin connecting a sales channel or fulfillment provider by returning an authorization URL to give the user, then keep polling connection status until it reports connected.

Instructions

Begin a browser-based connection (Printful, Shopify, TikTok Shop, Fourthwall). Shopify additionally requires shop_url, the merchant myshopify domain — ask for it before calling. Returns an authorization URL to give the user. THE CONNECTION IS NOT FINISHED WHEN THIS RETURNS. You must keep polling check_connection_status (passing the same provider_uuid) until it reports connected, then tell the user. The browser tab where they authorize is NOT this conversation and cannot report back to you, so polling is the only way you or they will learn it worked. Poll every few seconds, up to about two minutes, and if it has not landed by then ask whether they finished authorizing rather than giving up silently. If they need to create an upstream account first, let them, then call this again for a fresh link.

[#6d4006]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesWhich family this provider belongs to (from list_connectable_providers.family).
shop_urlNoRequired for Shopify only: the merchant's myshopify domain, e.g. your-store.myshopify.com. Ask the user for it; it is the domain in their Shopify admin URL, not their custom storefront domain. Omit for every other provider.
workspaceNoWorkspace uuid the store lives in (agency accounts) — use the store's workspace.uuid from list_my_stores. Omit only for single-workspace accounts; omitting it on a multi-workspace account targets the Default workspace and the call will fail to find a store that lives elsewhere.
store_nameNoName for a NEW store, when connecting fulfillment without an existing store_uuid.
store_uuidNoStore to attach to. Required for sales_channel. For fulfillment, omit it together with store_name to create a new store.
callback_urlNoOMIT THIS. The platform fills in the callback registered with the provider, and for Shopify that registered URL is the only one that works — anything else is refused, either by us or by Shopify with an error naming neither what was sent nor what was wanted. Set it only if you have been given a specific URL to use.
provider_uuidYesProvider uuid (from list_connectable_providers).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.15.2

TDQS

A4.1/5.0
Behavior5/5

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

Annotations provide only openWorldHint=true, so the description carries the burden and does so: it discloses that the connection is NOT finished on return, that the browser tab cannot report back, the polling cadence (~2 minutes), the fallback if it hasn't landed, and the callback_url restriction. This is exactly the async/failure-mode context an agent needs.

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?

Cap-heavy but front-loaded and well ordered: what it does, the Shopify precondition, the return value, then the polling obligation. The trailing unlabeled artifact '[#6d4006]' is stray noise that slightly detracts from otherwise disciplined prose.

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?

With no output schema and only a sparse annotation, the description fills the gaps completely: it names the return value (authorization URL), the required follow-up tool and argument, and the terminal condition. Nothing needed to call and complete this flow 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 every parameter including shop_url and callback_url is already documented in the schema. The description restates the Shopify shop_url precondition and reinforces omitting callback_url, adding emphasis but little new semantics beyond the schema baseline.

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?

States a specific verb (Begin) plus resource (browser-based connection) and enumerates the providers it covers (Printful, Shopify, TikTok Shop, Fourthwall), so the agent knows exactly what it starts. It does not distinguish itself from the very similar siblings connect_fulfillment_provider and connect_sales_channel, so sibling differentiation is missing.

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 clear operational context: ask for shop_url before calling for Shopify, poll check_connection_status after, re-call for a fresh link if the user must first create an upstream account. It is strong on sequencing but never says when to prefer this over the two connect_* sibling tools.

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