Skip to main content
Glama

List order requests

list_order_requests
Read-onlyIdempotent

List the order requests visitors sent through the order form in the chat: number, status, products, name and phone. An order request is not paid; the team confirms it with the visitor. Needs the Standard plan or higher.

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_order_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many requests to return (1-100, default 25).
statusNoOnly requests with this status. open means new or confirmed. Leave it out for all.
website_idNoNumeric id of the website, from list_websites. Omit to use the account's primary website.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds meaningful context beyond them: the semantic distinction that an order request is unpaid and requires team confirmation, plus an account-plan prerequisite that affects whether the call will succeed at all.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the operation and its output fields, then the domain caveat, then the plan requirement. No filler or redundant restatement of the title.

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, listing the returned fields (number, status, products, name, phone) fills a real gap, and the plan requirement covers a common failure mode. Ordering and pagination behavior are left implicit, but limit is documented in the schema.

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%, including the enum semantics for status and the website_id fallback, so the schema carries the parameter burden. The description adds no parameter-level detail beyond the returned field list, so the baseline of 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 ("List the order requests visitors sent through the order form in the chat") and enumerates the returned fields, so the agent knows exactly what comes back. It stops short of differentiating itself from the sibling get_order_request, but the plural 'list' scope is unambiguous.

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?

Usage context is implied by the domain explanation ("An order request is not paid; the team confirms it with the visitor") and the plan entitlement ("Needs the Standard plan or higher"), which is a real gating check. There is no explicit when-to-use-this-vs-alternatives guidance, e.g. pointing to get_order_request for a single request or update_order_request to change status.

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.

Resources