Skip to main content
Glama

list_payment_links

Read-onlyIdempotent

List payment links newest first, with optional status filters to review paid orders or find abandoned checkouts.

Instructions

List your payment links, newest first, optionally filtered by status.

Use statuses=['Complete', 'Delivered'] to review paid orders, or statuses=['Pending']
to find checkouts a buyer started but never finished; omit `statuses` for every state.
When you already know the reference IDs, use `get_payment_link` or
`get_payment_links_batch` instead of paging through this.

Wayl returns no total count, so do not treat the number of rows as the number of
orders. Keep paging with `nextSkip` while `hasMore` is true — it is a heuristic, true
whenever a full page came back.

Rows are raw Wayl records: `total` is a string, and only status Complete or Delivered
means paid. Nothing here reports which environment a link belongs to, so test and live
orders look identical — confirm with `check_order_paid` before delivering anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoHow many to skip before this page starts. Pass the `nextSkip` returned by the previous call.
takeNoHow many links to return.
statusesNoFilter by payment status.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations already declare readOnly, openWorld, and idempotent, but the description adds substantial behavioral context beyond that: no total count returned, `hasMore` is a heuristic, `total` is a string, only status Complete/Delivered means paid, and the environment is not reported. The warning to confirm with `check_order_paid` before delivery is extra value not present in 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?

Every sentence carries unique operational guidance, and the description is front-loaded with the core purpose. While it is longer than minimal, there is no filler or repetition; it earns its length with dense, useful detail.

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

Completeness5/5

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

Given the tool's complexity, the description covers all critical operational aspects: pagination behavior, status semantics, raw record format, environment ambiguity, and cross-tool confirmation via `check_order_paid`. The output schema exists, so no need to describe return values, making this complete.

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?

Schema descriptions cover all three parameters, so the baseline is 3. However, the description adds meaningful usage semantics for `statuses` (recommended combinations and omission for all states) and explains the `skip`/`nextSkip` pagination pattern, going beyond what the schema provides.

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 description opens with a specific verb and resource: 'List your payment links, newest first, optionally filtered by status.' It clearly states the sort order and filtering capability. It also distinguishes itself from siblings by explicitly naming `get_payment_link` and `get_payment_links_batch` as alternatives when you already know reference IDs.

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

Usage Guidelines5/5

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

The description provides direct when-to-use guidance: `statuses=['Complete', 'Delivered']` for paid orders, `statuses=['Pending']` for abandoned checkouts, and omit `statuses` for all states. It also explicitly names alternatives (`get_payment_link`, `get_payment_links_batch`) and warns against treating row count as order count, making the usage context unmistakable.

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/muthanii/waylMCP'

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