shopify_get_orderFetch a single Shopify order by numeric ID, returning line items, customer info, fulfillment status, totals, and shipping address via the Admin API.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Order ID | |
| _shop | Yes | Shop domain (e.g., mystore.myshopify.com) | |
| _apiKey | Yes | Shopify Admin API access token |
| Name | Required | Description | Default |
|---|---|---|---|
| order | No | Order details |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "order": {
+ "description": "Order details",
+ "properties": {
+ "created_at": {
+ "description": "Creation timestamp",
+ "type": "string"
+ },
+ "currency": {
+ "description": "Currency code",
+ "type": "string"
+ },
+ "customer": {
+ "description": "Customer details",
+ "type": "object"
+ },
+ "email": {
+ "description": "Customer email",
+ "type": "string"
+ },
+ "financial_status": {
+ "description": "Financial status",
+ "type": "string"
+ },
+ "fulfillment_status": {
+ "description": "Fulfillment status",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "id": {
+ "description": "Order ID",
+ "type": "number"
+ },
+ "line_items": {
+ "description": "Order line items",
+ "type": "array"
+ },
+ "order_number": {
+ "description": "Order number",
+ "type": "number"
+ },
+ "total_price": {
+ "description": "Total order price",
+ "type": "string"
+ },
+ "updated_at": {
+ "description": "Last update timestamp",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "type": "object"
+}Input schema / examplesAdded value: +[
+ {
+ "_apiKey": "your-shopify-api-key",
+ "_shop": "mystore.myshopify.com",
+ "id": 1071559878
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety and idempotency are clear. The description adds value by specifying the exact fields returned (line items, customer info, fulfillment status, totals, shipping address) and that it uses the Admin API. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence of 22 words, front-loaded with verb and resource, and contains zero filler. Every word adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple fetch tool with 3 required parameters and an output schema (not shown but noted), the description sufficiently covers what the tool returns. No additional details are needed; it is complete for the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with each parameter having a clear description. The description reinforces that 'id' is a numeric ID but adds no new semantic detail beyond the schema. Baseline score of 3 is appropriate given full schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Fetch'), the resource ('a single Shopify order by numeric ID'), and explicitly lists returned data (line items, customer info, fulfillment status, totals, shipping address). It distinguishes from siblings like shopify_list_orders (list vs single) and shopify_get_product (different resource).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description is clear about what the tool does and implicitly when to use it (fetching a single order by ID). However, it does not explicitly state when not to use it or mention alternatives (e.g., shopify_list_orders for multiple orders). Still, the context makes usage straightforward.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.