Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_payment_order_list

Read-onlyIdempotent

Retrieve a paginated list of orders with filters for status, payment status, payment mode, date range, contact, funnel products, and source. Supports pagination via limit and offset.

Instructions

List Orders The "List Orders" API allows to retrieve a paginated list of orders. Customize your results by filtering orders based on name, alt type, order status, payment mode, date range, type of source, contact, funnel products or paginate through the list using the provided query parameters. This endpoint provides a straightforward way to explore and retrieve order information. Endpoint: GET /payments/orders (Version header: v3; source: v3/payments-v3.json) OAuth scopes: payments/orders.readonly Pagination params: limit, offset — pass them to page through full result sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
altIdYesAltId is the unique identifier e.g: location id.
endAtNoClosing interval of orders.
limitNoThe maximum number of items to be included in a single page of results
offsetNoThe starting index of the page, indicating the position from which the results should be retrieved.
searchNoThe name of the order for searching.
statusNoOrder status.
startAtNoStarting interval of orders.
sourceIdNoSource id
contactIdNoContact id for filtering of orders.
locationIdNoLocationId is the id of the sub-account.
paymentModeNoMode of payment.
paymentStatusNoPayment Status of the Order
funnelProductIdsNoFunnel product ids separated by comma.
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds endpoint info and OAuth scopes but no additional behavioral traits beyond what annotations cover. No contradictions.

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?

The description is about 5 sentences, front-loaded with title and purpose. It includes endpoint and OAuth details which are useful but somewhat redundant. Could be slightly more concise.

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?

For a list tool with 13 parameters and no output schema, the description adequately explains filtering capabilities and pagination (limit/offset mentioned). Missing response structure but annotations keep it safe. Mostly complete.

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 coverage is 100% (all 13 parameters have descriptions). The description lists filter categories (name, status, payment mode, etc.) but does not add meaning beyond the schema. Baseline 3 due to full schema coverage.

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 title 'List Orders' and description clearly state it retrieves a paginated list of orders with filtering options. It distinguishes itself from sibling tools like ghl_payment_order_get (single order) and ghl_payment_order_list_fulfillments (specific list).

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?

The description implies usage for listing orders but does not explicitly state when to use this tool versus alternatives like ghl_payment_order_get or ghl_payment_order_list_notes. No when-not-to-use guidance is provided.

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/zackscriven/ghl-mcp-server'

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