Skip to main content
Glama
zenskar

Zenskar MCP Server

Official
by zenskar

listAllPayments

listAllPayments

Retrieve a paginated list of all payments and refunds with filters by customer, amount, status, date, and more, plus sorting.

Instructions

Retrieve a paginated list of all payments, including refund records, with extensive filtering and sorting options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoThe cursor for pagination.
limitNoMaximum number of payments to return per page (defaults to 10).
searchNoGeneral search query.
sort_keyNoKey to sort the results by (e.g., 'id').
sort_typeNoSort order type (e.g., 'asc').
orderNoOrder of results (e.g., '-created_at').-created_at
idNoFilter by payment ID.
customer_idNoFilter by customer ID.
connector_idNoFilter by connector ID.
external_id__ilikeNoCase-insensitive partial match for external ID.
payment_methodNoFilter by payment method (e.g., 'card', 'cash', 'bank_transfer').
typeNoFilter by payment type (e.g., 'payment', 'refund').
amount__gteNoFilter by amount greater than or equal to.
amount__lteNoFilter by amount less than or equal to.
amount_refunded__gteNoFilter by amount refunded greater than or equal to.
amount_refunded__lteNoFilter by amount refunded less than or equal to.
currency_code__ilikeNoCase-insensitive partial match for currency code.
receipt_number__ilikeNoCase-insensitive partial match for receipt number.
statusNoFilter by payment status (e.g., 'success', 'failed').
autochargeNoFilter by auto-charge status.
parent_idNoFilter by parent payment ID.
timestamp__gteNoFilter by timestamp greater than or equal to (Unix time).
timestamp__lteNoFilter by timestamp less than or equal to (Unix time).
created_at__gteNoFilter by creation date greater than or equal to (ISO 8601).
created_at__lteNoFilter by creation date less than or equal to (ISO 8601).
invoice__idNoFilter by associated invoice ID.
invoice__bill_for_date__gteNoFilter by invoice billing date greater than or equal to (ISO 8601).
invoice__bill_for_date__lteNoFilter by invoice billing date less than or equal to (ISO 8601).
invoice__approved_at__gteNoFilter by invoice approval date greater than or equal to (ISO 8601).
invoice__approved_at__lteNoFilter by invoice approval date less than or equal to (ISO 8601).
customer__business_entity_idNoFilter by customer's business entity ID.
__userContextNoInternal user context for multi-tenant authentication and approval workflow
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions pagination and filtering but lacks details on rate limits, authentication, default behavior, or potential side effects.

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?

The description is a single concise sentence that efficiently communicates the tool's purpose without any wasted words.

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

Completeness2/5

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

Given the tool has 32 parameters and no output schema, the description is too brief. It does not explain pagination behavior, return structure, default sorting, or how to use the extensive filters effectively.

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 description coverage is 100%, so the baseline is 3. The description adds the fact that refund records are included, but otherwise does not enhance understanding beyond the schema.

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?

The description clearly states it retrieves a paginated list of payments including refunds, with filtering and sorting. It uses a specific verb and resource, but does not explicitly differentiate from sibling list tools like listInvoices or listPaymentMethods.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention context, prerequisites, or when not to use it.

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/zenskar/mcp-zenskar'

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