Skip to main content
Glama

List store orders

list_store_orders
Read-onlyIdempotent

Orders the RentADriver connector has seen on the WooCommerce, BigCommerce, Wix Stores or Squarespace stores connected to this account, with the booking status (booked / skipped / needs_funds / failed) and the linked delivery. Requires the store to be connected: https://rentadriver.ai/integrations/

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>"
    },
    "name": "list_store_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds response content (booking status and linked delivery) and the connection prerequisite, which is useful. It omits ordering, pagination, and default behavior, and its status list (booked/skipped/needs_funds/failed) is an incomplete subset of the schema enum, which adds mild noise rather than clarity.

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 sentences, front-loading what the tool returns and following with the prerequisite. Density is high but every clause carries information; the parenthetical status list is the only redundant part since it duplicates (incompletely) the schema enum.

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?

With no output schema, the description usefully sketches the return payload (orders, booking status, linked delivery) and states the connectivity prerequisite. Given annotations cover the safety profile, the main remaining gap is limit/pagination behavior and default ordering.

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 0%, so the description must carry parameter meaning. It does explain platform values (matching the enum) and partially explains the status domain, but it never mentions the limit parameter, its 200 maximum, or the pending/cancelled statuses, leaving a meaningful gap for a 3-parameter tool.

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?

The description names the resource (orders) and enumerates the exact source platforms (WooCommerce, BigCommerce, Wix Stores, Squarespace), which implicitly distinguishes it from the Shopify-specific sibling. 'Orders the connector has seen' is slightly vague about what 'seen' means (synced? fetched?), but an agent can identify the resource and scope.

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

Usage Guidelines3/5

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

It states a concrete prerequisite ('Requires the store to be connected') with a setup URL, which is genuine usage guidance. However, it never says when to prefer this over list_shopify_orders or book_store_order, nor any when-not conditions, so the alternative-selection guidance is only implied by the platform list.

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.