Skip to main content
Glama

get-orders

Retrieve Shopify store orders with filtering options for status and quantity to manage and analyze sales data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoany
limitNo

Implementation Reference

  • The execute function contains the main handler logic for get-orders tool. It validates input, builds GraphQL query based on status filter, fetches orders from Shopify API, formats the response including order details, customer info, and line items.
    execute: async (input: GetOrdersInput) => {
      try {
        const { status, limit } = input;
    
        // Build query filters
        let queryFilter = "";
        if (status !== "any") {
          queryFilter = `status:${status}`;
        }
    
        const query = gql`
          query GetOrders($first: Int!, $query: String) {
            orders(first: $first, query: $query) {
              edges {
                node {
                  id
                  name
                  createdAt
                  displayFinancialStatus
                  displayFulfillmentStatus
                  totalPriceSet {
                    shopMoney {
                      amount
                      currencyCode
                    }
                  }
                  subtotalPriceSet {
                    shopMoney {
                      amount
                      currencyCode
                    }
                  }
                  totalShippingPriceSet {
                    shopMoney {
                      amount
                      currencyCode
                    }
                  }
                  totalTaxSet {
                    shopMoney {
                      amount
                      currencyCode
                    }
                  }
                  customer {
                    id
                    firstName
                    lastName
                    email
                  }
                  shippingAddress {
                    address1
                    address2
                    city
                    provinceCode
                    zip
                    country
                    phone
                  }
                  lineItems(first: 10) {
                    edges {
                      node {
                        id
                        title
                        quantity
                        originalTotalSet {
                          shopMoney {
                            amount
                            currencyCode
                          }
                        }
                        variant {
                          id
                          title
                          sku
                        }
                      }
                    }
                  }
                  tags
                  note
                }
              }
            }
          }
        `;
    
        const variables = {
          first: limit,
          query: queryFilter || undefined
        };
    
        const data = (await shopifyClient.request(query, variables)) as {
          orders: any;
        };
    
        // Extract and format order data
        const orders = data.orders.edges.map((edge: any) => {
          const order = edge.node;
    
          // Format line items
          const lineItems = order.lineItems.edges.map((lineItemEdge: any) => {
            const lineItem = lineItemEdge.node;
            return {
              id: lineItem.id,
              title: lineItem.title,
              quantity: lineItem.quantity,
              originalTotal: lineItem.originalTotalSet.shopMoney,
              variant: lineItem.variant
                ? {
                    id: lineItem.variant.id,
                    title: lineItem.variant.title,
                    sku: lineItem.variant.sku
                  }
                : null
            };
          });
    
          return {
            id: order.id,
            name: order.name,
            createdAt: order.createdAt,
            financialStatus: order.displayFinancialStatus,
            fulfillmentStatus: order.displayFulfillmentStatus,
            totalPrice: order.totalPriceSet.shopMoney,
            subtotalPrice: order.subtotalPriceSet.shopMoney,
            totalShippingPrice: order.totalShippingPriceSet.shopMoney,
            totalTax: order.totalTaxSet.shopMoney,
            customer: order.customer
              ? {
                  id: order.customer.id,
                  firstName: order.customer.firstName,
                  lastName: order.customer.lastName,
                  email: order.customer.email
                }
              : null,
            shippingAddress: order.shippingAddress,
            lineItems,
            tags: order.tags,
            note: order.note
          };
        });
    
        return { orders };
      } catch (error) {
        console.error("Error fetching orders:", error);
        throw new Error(
          `Failed to fetch orders: ${
            error instanceof Error ? error.message : String(error)
          }`
        );
      }
    }
  • Input schema definition using Zod for validating get-orders parameters. Accepts status (enum: any/open/closed/cancelled, default: any) and limit (number, default: 10).
    // Input schema for getOrders
    const GetOrdersInputSchema = z.object({
      status: z.enum(["any", "open", "closed", "cancelled"]).default("any"),
      limit: z.number().default(10)
    });
    
    type GetOrdersInput = z.infer<typeof GetOrdersInputSchema>;
  • src/index.ts:123-135 (registration)
    MCP server tool registration for get-orders. Registers the tool with its schema and wraps the execute function to return properly formatted JSON response.
    server.tool(
      "get-orders",
      {
        status: z.enum(["any", "open", "closed", "cancelled"]).default("any"),
        limit: z.number().default(10)
      },
      async (args) => {
        const result = await getOrders.execute(args);
        return {
          content: [{ type: "text", text: JSON.stringify(result) }]
        };
      }
    );
  • Tool definition object with name, description, schema, and initialize method for setting up the GraphQL client dependency.
    const getOrders = {
      name: "get-orders",
      description: "Get orders with optional filtering by status",
      schema: GetOrdersInputSchema,
    
      // Add initialize method to set up the GraphQL client
      initialize(client: GraphQLClient) {
        shopifyClient = client;
      },
  • Initialization of getOrders tool with the Shopify GraphQL client before tool registration.
    getOrders.initialize(shopifyClient);
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/anass319/shopify-MCP'

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