Skip to main content
Glama

create_order

Directly create a Shopify order with explicit line-item pricing, bypassing draft orders. Use for historical imports or phone/in-person sales when automatic tax and shipping calculation is not needed.

Instructions

Create a real Shopify order directly, bypassing the draft-order flow. Each line item is either a variant reference (variantId + quantity) or a custom item (title + priceSet + quantity). Use when you need to import historical orders, record a phone/in-person sale, or create an order without involving Shopify's checkout pricing engine. For interactive carts where Shopify should compute taxes/shipping/discounts, use create_draft_order then complete_draft_order instead. Defaults: PENDING financial status, customer not notified, inventory decremented respecting each variant's oversell policy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lineItemsYesAt least one line item. Each is either a variant reference (variantId + quantity) or a custom item (title + priceSet + quantity). Use draft orders (create_draft_order → complete_draft_order) when you want Shopify to handle pricing/taxes automatically; use this tool when you need to create an order directly with explicit line-item pricing.
emailNoCustomer email for the order. Recommended even when customerId is set.
customerIdNoGID of an existing customer to attach. Get one from list_customers. Optional.
tagsNoTags applied to the new order.
noteNoInternal staff-only note attached to the order.
financialStatusNoInitial financial status to record. Defaults to PENDING if omitted. Use PAID when capturing payment outside Shopify (manual offline payment).
sendReceiptNoWhether to email the customer a receipt for the new order.
inventoryBehaviourNoHow inventory is handled. BYPASS: don't touch inventory. DECREMENT_OBEYING_POLICY (default): decrement and respect each variant's oversell policy. DECREMENT_IGNORING_POLICY: decrement always, even past zero.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses key defaults: financial status defaults to PENDING, customer not notified, inventory behavior respects oversell policy. However, it does not mention required permissions, webhook triggers, or whether customer validation occurs. Still above average for a mutation tool.

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?

Two compact sentences plus a terse defaults line. Every sentence adds value: purpose, use cases, alternatives, and key defaults. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters and no output schema, the description should explain what the tool returns (e.g., the created order object). It omits return value entirely, leaving the agent to infer from the schema's nested structure. This is a notable gap for a complex creation tool.

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 coverage is 100% with descriptions for all parameters. The description adds context beyond schema by explaining the distinction between variant line items and custom items, and reiterating when to use draft orders. This provides decision-making context not present in the schema alone.

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 the tool creates a real Shopify order directly, bypassing draft-order flow. It specifies the verb 'create' and resource 'Shopify order', distinguishing it clearly from sibling tools like create_draft_order.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use (importing historical orders, recording phone/in-person sales) and when-to-use-alternative (use create_draft_order for interactive carts where Shopify computes taxes/shipping/discounts). Names the alternative tool explicitly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/miller-joe/shopify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server