Skip to main content
Glama

List Shopify orders

list_shopify_orders
Read-onlyIdempotent

Orders the RentADriver app for Shopify has seen on the shops connected to this account, with the booking status (booked / skipped / needs_funds / failed) and the linked delivery. Requires the app to be installed on the store: https://rentadriver.ai/integrations/shopify

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": "list_shopify_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description still adds real value beyond that by disclosing the integration prerequisite (the app must be installed on the store, with a link) and by characterizing the payload domain (booking status values plus the linked delivery).

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 compact sentences with no filler, and the substantive payload description leads. The broken grammar of the opening clause costs a little comprehension, but nothing is redundant.

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?

With no output schema, the description does sketch what comes back (orders with booking status and linked delivery), which is appropriate. It does not cover default ordering, default limit, or what the limit actually bounds, so an agent must inspect the schema and guess at result volume for a zero-required-parameter listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It lists several status values (booked / skipped / needs_funds / failed) but omits pending and cancelled, which do exist in the enum, and it says nothing at all about the limit parameter (max 200, default behavior, pagination). It therefore only partially and inconsistently compensates for the schema gap.

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 sentence names the resource (Shopify orders seen across the shops connected to this account) and the salient fields returned (booking status, linked delivery), so the purpose is discernible despite the ungrammatical 'Orders the RentADriver app ... has seen' opening. It does not differentiate from the sibling list_store_orders, leaving the agent to infer which of the two listing tools applies to a Shopify-connected shop.

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?

There is no when-to-use, when-not-to-use, or alternative-naming guidance; the only usage-adjacent content is the prerequisite that the Shopify app must be installed on the store. An agent still cannot tell from the description whether to prefer this tool or list_store_orders for a given request.

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.