Youzan MCP integration for AI agents.
Connect AI agents to Youzan through 9 structured actions, including get item, get refund, and get order. Review authentication, inputs, workflows, and safety…
- ACTION CONTRACTS
- 9
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Youzan integration exposes
The Youzan Agent App exposes 9 provider-backed actions for marketing work. Its current contract lets an authorized agent get a youzan item by its item id, get a youzan refund or after-sale record by its refund id, and get a youzan order by its order id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Youzan account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Youzan capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_itemREADGet a Youzan item by its item ID.
INPUTS: itemId
get_refundHIGH IMPACTGet a Youzan refund or after-sale record by its refund ID.
INPUTS: refundId / includeAllConsultMessages
get_orderREADGet a Youzan order by its order ID.
INPUTS: orderId
get_order_logisticsREADGet all express or local-delivery packages and tracking details for a Youzan order.
INPUTS: orderId / sourceId
get_shopREADGet the identity and basic profile of the connected Youzan shop.
list_inventory_itemsREADList shelved or sold-out items from a Youzan store inventory.
INPUTS: status / query / orderBy / updatedAfter / updatedBefore
list_onsale_itemsREADList items currently visible for sale in a Youzan online or physical store.
INPUTS: kdtId / channel / title / itemIds / itemCodes
list_ordersREADList Youzan orders using status, time, item, delivery, and text filters.
INPUTS: status / orderId / keywords / itemId / expressType
list_refundsREADList Youzan refund and after-sale records using order, status, and time filters.
INPUTS: orderId / refundId / status / demand / createdAfter
INPUT CONTRACTS
Know what the action needs before it runs.
get_item
itemIdOPTIONAL- The Youzan item ID.
get_refund
refundIdREQUIRED- The Youzan refund ID.
includeAllConsultMessagesOPTIONAL- Whether to include all buyer and seller consultation messages.
get_order
orderIdOPTIONAL- The Youzan order ID.
get_order_logistics
orderIdREQUIRED- The Youzan order ID.
sourceIdOPTIONAL- The Youzan order source: 1001 for catering or 1002 for other stores. Defaults to 1002.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Item
Get a Youzan item by its item ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_itemControl Get Refund
Get a Youzan refund or after-sale record by its refund ID. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
get_refundVerify with Get Order
Get a Youzan order by its order ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_orderSAFETY BOUNDARY
Operate Youzan with explicit limits
- Authorize Youzan with Custom credentials and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `get_refund` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Youzan rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Youzan task completed successfully.
CONNECTION MODEL
Custom credentials
Youzan uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Youzan.