Skip to main content
Glama

get_payments

Read-onlyIdempotent

Retrieve a paginated list of payments, sorted by most recent, with filters for product type, user, affiliate, product ID, and creation date range.

Instructions

🟢 READ-ONLY · Payments · GET /v2/payments

Get payments

Returns a list with all the payments. The payments are in sorted order, with the most recently created payment appearing first, and the list is paginated, with a default limit of 50 payments per page. To refine the list of payments, there are a number of query params outlined in the following section; In case more than one Query param is provided, then all of them will be applied (AND operator).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoFilter by the page number. In case page number is higher than the maximum one, the results of last page will be returned
user_idNoFilter by user id or email (encoded string)
product_idNoFilter by product id
affiliate_idNoFilter by affiliate id or email (encoded string)
product_typeNoFilter by product type
created_afterNoFilter by payment creation after the given datetime (expected in UNIX timestamp format)
created_beforeNoFilter by payment creation before the given datetime (expected in UNIX timestamp format)
items_per_pageNoFilter by the items per page number
Behavior4/5

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

In addition to annotations (readOnly, idempotent, not destructive), description explains pagination, sorting by creation date, default limit of 50, and AND logic for filters.

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?

Front-loaded with key info (read-only, list, sorting, pagination). Some verbosity from emoji and line breaks, but overall efficient.

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?

Given 8 parameters with full schema coverage and no output schema, description adequately covers behavior (pagination, sorting, filtering logic) for a list tool.

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 covers all 8 parameters with descriptions. Description adds context about filtering and AND operator but does not provide additional detail beyond schema.

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?

Description clearly states it retrieves a list of all payments, sorted and paginated. Distinguishes from sibling get_payment (singular) by indicating scope.

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?

Describes when to use (listing payments) and filtering behavior, but does not explicitly exclude alternatives or mention when to use sibling tools like get_payment.

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/ohneben/Learnworlds-MCP'

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