Skip to main content
Glama

list_payment_link_payments

Read-onlyIdempotent

List payments received through a payment link, newest first. Amounts use the returned currency's minor units. Invoice IDs can be used to look up the resulting invoices.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "list_payment_link_payments"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are ordered newest first, amounts are in the returned currency's minor units, and resulting invoices are reachable via invoice IDs. It omits pagination behavior despite an offset parameter.

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?

Three short sentences, front-loaded with the core action and scope, with no filler. The invoice-ID sentence is slightly tangential to invocation but earns its place as follow-up guidance.

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 should shoulder more of the return-value burden; it covers currency units and invoice linkage but not pagination beyond the bare offset parameter, nor what a payment record includes. Adequate for a simple two-parameter list tool, but not complete.

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 and largely does not meet it. It never states that 'id' is the payment link identifier (plausibly confusable with a payment or invoice ID given sibling tools) and never explains 'offset' as a pagination cursor; the only related sentence is about invoice IDs in the response, not inputs.

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 payments received through a payment link') plus ordering ('newest first'), which scopes it apart from the generic payment-list siblings. It stops short of explicitly naming a sibling or contrast case, so it lands at a clear-but-not-differentiating 4.

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 is only implied by the resource scope: an agent can infer this is the tool for payments tied to a payment link. There is no explicit when-to-use, when-not-to-use, or pointer to list_invoice_payments/list_appointment_payments for adjacent cases.

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