Skip to main content
Glama
kisasa

Shopify MCP Server

by kisasa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-customer-orders

Retrieve orders for a specific customer by numeric ID, using field selection and pagination to limit response size.

Instructions

Get orders for a specific customer. Supports field selection via 'fields' to reduce response size.

Input Schema

NameRequiredDescriptionDefault
afterNoCursor for forward pagination
limitNoNumber of orders to return (default 10, max 250)
beforeNoCursor for backward pagination
fieldsNoIMPORTANT: Always specify this to minimize token usage and avoid flooding context with unnecessary data. Only the listed fields will be fetched from the API and returned. 'id' is always included. If you are unsure which fields are needed, ask the user before fetching all fields. Example: ["id", "name"] returns only order GID and name. Available: id, name, createdAt, financialStatus, fulfillmentStatus, totalPrice, subtotalPrice, shippingPrice, tax, customer, lineItems, tags, note
reverseNoReverse the sort order
sortKeyNoSort key for orders
countOnlyNoIMPORTANT: Use this to check result set size before fetching data. Returns only { count: N } without any resource data, saving significant context. Recommended before paginating large result sets.
customerIdYesNumeric customer ID (e.g. 7832529321). Do not pass a full GID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden, but it only notes that 'fields' reduces response size. It says nothing about pagination behavior, the default/max page size, sort ordering, or that this is a read-only operation — all of which matter for an 8-parameter listing tool.

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?

Two short sentences with the scope up front and the optimization tip second. Nothing is wasted, though it is arguably too terse given the tool's complexity.

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

Completeness2/5

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

Eight parameters, no annotations, and no output schema — yet the description covers only customer scoping and field projection. Pagination, count-only mode, sorting, and the read-only nature are all left to the schema, which is thin compensation for a tool with this much surface area.

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 the schema already documents every parameter in detail, including the strongly emphasized 'fields' and 'countOnly'. The description's only parameter remark (field selection shrinks responses) merely restates the schema, so baseline 3 applies.

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 and resource ('Get orders') scoped to 'a specific customer', which partially separates it from siblings like get-orders. However, it never explicitly contrasts itself with get-orders or get-fulfillment-orders, so the differentiation is implied rather than stated.

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

Usage Guidelines2/5

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

No when-to-use guidance against the many sibling order-listing tools, and no mention of the prerequisites or recommended workflow (e.g. countOnly before paginating) that the schema considers important. The agent must infer that this is the per-customer variant of get-orders.

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