Skip to main content
Glama

Get Store Orders

get_orders
Read-only

Lists the orders from the company's connected online stores in a date range: each order's number, date, statuses, platform, currency, totals, discounts, refunds and line items. Buyers' details are not included. limit caps the rows (1 to 100, default 20); for the next page pass the returned cursor with the same start, end and limit. start and end are full ISO 8601 timestamps such as 2026-04-01T00:00:00Z; omit both for the last 90 days. Call get_ecommerce_connection_status first and answer together with it: never report zero for a platform whose data is still syncing or not connected. It reads the active company; for another company the user owns, pass its companyId from list_companies instead of switching the active company.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoOPTIONAL end as a FULL ISO 8601 timestamp WITH time + timezone, e.g. '2026-04-30T23:59:59Z'. Never date-only. Omit alongside `start` to fall back to the rolling 90-day window.
limitNomax rows (1-100); omit for the default
startNoOPTIONAL start as a FULL ISO 8601 timestamp WITH time + timezone, e.g. '2026-04-01T00:00:00Z'. Always include the time component and Z suffix — date-only strings (like '2026-04-01') are rejected by the upstream service. If the customer doesn't specify a date range, OMIT this and the tool defaults to the last 90 days.
cursorNoOPTIONAL. The cursor a previous call returned, for the next page; keep start, end and limit the same.
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
companyIdNoOPTIONAL. The doolaCompanyId (an id like '30E5c1AQA326uOuDlsic4No7zZ5'). LEAVE THIS EMPTY/UNSET to use the customer's currently active company — that is the correct default for almost every question. Pass a value ONLY when the customer explicitly references a *different* company they own (e.g. 'show me transactions for my other company X'). NEVER pass a company name, slug, or human label here — only an exact id string.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "OPTIONAL. The cursor a previous call returned, for the next page; keep start, end and limit the same.",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"max rows (1-100, default 50)"New value: +"max rows (1-100); omit for the default"
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description nonetheless adds real context: buyers' details are excluded from results, and reporting zeros for a still-syncing platform is explicitly forbidden. It does not describe response ordering or whether partial pages can occur, which keeps it short of a 5 for an eight-parameter list 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?

Purpose is front-loaded in the first sentence and each subsequent sentence covers a distinct concern: scope exclusion, pagination, date fallback, prerequisite call, company selection. It is dense but not padded, with only mild redundancy against the schema's own ISO timestamp wording.

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

Completeness5/5

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

For an eight-parameter, no-required-argument tool with no output schema, the description supplies both the shape of the return payload and the cross-tool sequencing needed to interpret it honestly. The three analytics-only parameters are fully documented in the schema, so their absence from the prose is not a gap.

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 description coverage is 100%, so the baseline is 3, but the description contributes the one datum the schema omits — the default of 20 rows — alongside the page-continuation rule (reuse the returned cursor with the same start, end and limit). The ISO 8601 guidance and companyId semantics largely restate the schema, so the added value is real but incremental.

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 opens with a specific verb and resource ('Lists the orders from the company's connected online stores in a date range') and then enumerates the returned fields (number, date, statuses, platform, currency, totals, discounts, refunds, line items). This distinguishes it clearly from get_orders_time_series (aggregates) and get_ecommerce_connection_status (connection state), so an agent can select it without opening a schema.

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?

It names an explicit prerequisite sibling ('Call get_ecommerce_connection_status first and answer together with it'), states a hard exclusion ('never report zero for a platform whose data is still syncing or not connected'), and routes the different-company case to list_companies/passing companyId instead of switching the active company. Defaults for a missing date range are also spelled out, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.