Skip to main content
Glama
Sign In

Paddle

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Paddle List Transactions

paddle_list_transactions
Read-onlyIdempotent

Return bounded Paddle transactions with customer, subscription, origin, collection mode, currency, totals, payment, and processing status. Answers which payments completed, remain past due, or were canceled.

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": {
      "status": "completed",
      "_apiKey": "pdl_sdbx_apikey_your-key",
      "per_page": 20,
      "_environment": "sandbox"
    },
    "name": "paddle_list_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoPagination cursor from meta.pagination.next
statusNo
_apiKeyYesPaddle Billing API key with read permission for the resource
per_pageNoResults per page, default 20 and maximum 30
customer_idNoPaddle customer ID beginning ctm_
_environmentNoPaddle environment; defaults to production
subscription_idNoPaddle subscription ID beginning sub_

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive. Description adds return field context (customer, subscription, etc.) but doesn't disclose pagination behavior, rate limits, or auth details beyond schema. With annotations covering safety, this is moderate added value.

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?

Two sentences, front-loaded with purpose. Field list is dense but informative. Second sentence provides use case efficiently. No wasted words.

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?

For a list tool with 7 parameters and no output schema, description covers purpose and return fields but omits filtering capabilities (status, customer_id, subscription_id) and pagination. Schema fills gaps, but description could be more complete regarding how to use filters.

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 86%, so parameters are well-documented in schema. Description adds no parameter details; baseline 3 when schema does the heavy lifting.

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 'Return' and resource 'Paddle transactions' with scope 'bounded'. Lists returned fields, which helps distinguish from sibling list tools like paddle_list_customers. Lacks explicit sibling differentiation but resource is clear.

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?

Provides a use case ('Answers which payments completed, remain past due, or were canceled') but no explicit when-to-use or alternatives. Implied usage is clear but no exclusions.

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