Skip to main content
Glama

orders_list

Read-onlyDestructiveIdempotent

List ecommerce orders with filters for status, payment status, and date range. Access customer personal data only with explicit consent via force parameter.

Instructions

List ecommerce orders (GET /admin/api/ecommerce/v1/orders). Read-only. Optional filters: status (e.g. 'created', 'cancelled'), payment_status (e.g. 'paid', 'unpaid'), created_after (ISO8601), created_before (ISO8601). include_pii=false (default) strips customer email / name / address / phone / IP via whitelist. include_pii=true REQUIRES force=true alongside — passing include_pii=true without force=true is rejected (LLM-side PII-exfiltration gate; see SECURITY.md). MCP hosts surface force as a destructive-hint approval, which keeps prompt-injected include_pii=true calls behind operator consent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYes
statusNoOrder status filter (q.order.status.$eq).
payment_statusNoPayment status filter (q.order.payment_status.$eq).
created_afterNoISO8601 timestamp; orders created at or after (q.order.created_at.$gteq).
created_beforeNoISO8601 timestamp; orders created at or before (q.order.created_at.$lteq).
include_piiNoDefault false (strips PII via whitelist). Set true to keep customer email / name / address / phone in the response. Requires force=true.
forceNoRequired when include_pii=true (PII-access acknowledgement gate; see SECURITY.md). Ignored otherwise. Default false.
Behavior5/5

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

Discloses read-only nature, the destructive hint for force (PII gate), and the rejection mechanism for include_pii without force. Adds value beyond annotations.

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?

Front-loaded with purpose, each sentence adds value. Slightly long but efficient for the complexity.

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

Completeness4/5

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

Covers purpose, filters, security considerations. No output schema, but that's acceptable. Could mention pagination, but not required.

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?

Adds meaning to parameters by explaining filter options and the security gate for PII. The site parameter lacks description but is compensated by context.

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?

Clearly states 'List ecommerce orders' with specific HTTP method and endpoint, distinguishing it from sibling tools like order_get.

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

Usage Guidelines4/5

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

Provides optional filters and explains the special include_pii/force interaction, guiding appropriate use. Lacks explicit 'when not to use' but offers sufficient context.

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/runnel/voog-mcp'

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