Skip to main content
Glama
Sign In

Paddle

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Paddle List Customers

paddle_list_customers
Read-onlyIdempotent

Return bounded Paddle customer records with IDs, email addresses, names, status, locale, and creation or update timestamps. Answers which billing customers match an email or changed recently.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "buyer@example.com",
      "_apiKey": "pdl_sdbx_apikey_your-key",
      "per_page": 20,
      "_environment": "sandbox"
    },
    "name": "paddle_list_customers"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoPagination cursor from meta.pagination.next
emailNoExact customer email filter
statusNo
_apiKeyYesPaddle Billing API key with read permission for the resource
per_pageNoResults per page, default 20 and maximum 30
_environmentNoPaddle environment; defaults to production

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds that results are 'bounded' and lists returned fields, but it does not disclose pagination behavior, rate limits, or other operational traits beyond what annotations and the schema already provide.

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 two sentences, front-loaded with the core action and followed by a use-case summary. Every sentence contributes useful information with no redundant or filler text.

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?

With no output schema, the description usefully names the returned fields and the question the tool answers. Combined with rich annotations and high schema coverage, it is largely complete, though it omits sibling differentiation and pagination context that could help an agent choose and invoke it correctly.

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 83%, which is high enough that the schema itself documents most parameters. The description mentions email matching and recent changes, but does not add syntax, format, or constraint details beyond what the schema already provides, so baseline 3 is appropriate.

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 uses a specific verb and resource ('Return bounded Paddle customer records') and enumerates returned fields, so an agent knows exactly what the tool does. However, it does not differentiate this tool from sibling Paddle list tools such as paddle_list_subscriptions, paddle_list_transactions, or paddle_list_adjustments.

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?

The phrase 'Answers which billing customers match an email or changed recently' implies a usage context, but there is no explicit guidance on when to choose this tool over sibling list tools or when not to use it. Alternatives and exclusions are absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Paddle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources