Skip to main content
Glama
kisasa

Shopify MCP Server

by kisasa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-order-by-id

Retrieve a specific Shopify order by order number, numeric ID, or GID, and optionally select only needed fields to reduce response size and token usage.

Instructions

Get a specific order by ID. Supports field selection via 'fields' to reduce response size.

Input Schema

NameRequiredDescriptionDefault
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, currentTotalPrice, customer, shippingAddress, billingAddress, lineItems, tags, note, cancelReason, cancelledAt, updatedAt, returnStatus, processedAt, poNumber, discountCodes, metafields
orderIdYesAccepts order numbers (e.g. 77713), numeric IDs, or full GIDs (gid://shopify/Order/...)

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 provided, the description carries the full burden and says almost nothing behavioral: it does not confirm this is a read-only lookup, does not mention what happens for an unknown ID, and does not describe the returned payload. The one behavioral point it does make—that field selection reduces response size—is already stated more forcefully in the schema.

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, front-loaded with the core purpose and with zero filler. It is perhaps overly terse given the tool's role, but nothing is wasted.

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?

There is no output schema and no annotations, so the description is the only place to convey the return shape and safety profile—neither is covered. For a simple fetch tool the parameter schema compensates well, but the missing return/behavior detail leaves a real gap.

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%; the schema already explains accepted orderId formats (number, numeric ID, GID) and enumerates the fields option. The description's note about 'fields' reducing response size adds little beyond that, 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 a specific order by ID'), which implicitly separates it from the list-oriented sibling get-orders. It does not name any sibling explicitly, so the differentiation is inferred 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 guidance on when to prefer this over get-orders, get-order-transactions, or get-order-refund-details, and no prerequisites or error conditions mentioned. The only usage hint is that 'fields' should be supplied to trim the response.

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