Skip to main content
Glama

get_payment_links_batch

Read-onlyIdempotent

Retrieve up to 100 payment links by your reference IDs in a single call for batch order reconciliation. Returns found and missing IDs to identify unrecognized references quickly.

Instructions

Look up many payment links at once by your own reference IDs (1-100 per call).

Use this when reconciling a batch of orders — far cheaper than calling
`get_payment_link` in a loop. For a single order use `get_payment_link`, or
`check_order_paid` when the question is whether to deliver.

Reference IDs Wayl does not recognise are silently skipped rather than raising, so
`totalFound` below `totalRequested` is normal; the ones that came back missing are
listed under `missingReferenceIds`.

Returns Wayl's raw envelope — `data` alongside `totalRequested` and `totalFound` —
not the enriched record `get_payment_link` gives you. Rows carry no paid verdict:
only status Complete or Delivered counts as settled, and `total` is a string. This is
a POST that creates nothing, but it is not retried on a transient failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reference_idsYesYour own reference IDs — the ones you set when creating each link, not Wayl's internal `id`. Between 1 and 100 per call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations declare read-only and idempotent hints, but the description adds crucial behavior: unrecognized reference IDs are silently skipped, `totalFound` may be below `totalRequested` with missing IDs listed in `missingReferenceIds`, returns the raw envelope rather than enriched records, lacks a paid verdict, `total` is a string, and no retry on transient failures. These details far exceed the annotations.

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?

Each paragraph covers a distinct aspect: purpose/usage, missing-ID behavior, response envelope, status interpretation, and HTTP/no-retry semantics. The description is front-loaded with the primary purpose and is efficient given the rich behavioral nuances that need disclosure.

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?

For a batch lookup tool, the description covers batch limits, silent skip behavior, response shape (`data`, `totalRequested`, `totalFound`, `missingReferenceIds`), status settlement rules (Complete/Delivered), `total` as a string, and retry semantics. This is complete guidance for safe invocation.

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?

The input schema already fully describes `reference_ids`, including its meaning (your own IDs, not Wayl's internal `id`) and constraints (1-100 per call). The description adds context about behavior with unrecognized IDs, but the parameter itself is fully covered by the schema, so the baseline for 100% coverage applies.

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 concrete action: 'Look up many payment links at once by your own reference IDs (1-100 per call).' It explicitly contrasts with `get_payment_link` for single orders and `check_order_paid` for delivery decisions, distinguishing this batch tool from siblings.

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 states 'Use this when reconciling a batch of orders — far cheaper than calling get_payment_link in a loop' and directs to `get_payment_link` or `check_order_paid` when appropriate. This explicit when-to-use guidance covers both recommended contexts and alternatives.

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