Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

list_reports

Read-only

Retrieve and filter financial reports from Paddle Billing with pagination, sorting, and status-based filtering capabilities.

Instructions

This tool will list reports in Paddle.

Use the maximum perPage by default (200) to ensure comprehensive results. Filter reports by status as needed. Results are paginated - use the 'after' parameter with the last ID from previous results to get the next page. Sort and order results using the orderBy parameter.

Amounts are in the smallest currency unit (e.g., cents).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoReturn entities after the specified Paddle ID when working with paginated endpoints.
orderByNoOrder returned entities by the specified field and direction.
perPageNoSet how many entities are returned per page. Returns the maximum number of results if a number greater than the maximum is requested.
statusNoReturn entities that match the specified status. Use a comma-separated list to specify multiple status values.

Implementation Reference

  • The handler function implementing the list_reports tool logic. It lists reports using the Paddle SDK's reports.list method, fetches the first page of results, computes pagination data, and returns paginated reports or an error.
    export const listReports = async (paddle: Paddle, params: z.infer<typeof Parameters.listReportsParameters>) => {
      try {
        const collection = paddle.reports.list(params);
        const reports = await collection.next();
        
        const pagination = paginationData(collection);
        return { pagination, reports };
      } catch (error) {
        return error;
      }
    };
  • The schema definition for the list_reports tool, including the method name, human-readable name, description prompt, Zod parameters schema reference, and required permissions/actions for reports listing.
      method: "list_reports",
      name: "List reports",
      description: prompts.listReportsPrompt,
      parameters: params.listReportsParameters,
      actions: {
        reports: {
          read: true,
          list: true,
        },
      },
    },
  • src/api.ts:85-85 (registration)
    Registration of the listReports handler function in the internal toolMap used by PaddleAPI.run method to dispatch tool calls.
    [TOOL_METHODS.LIST_REPORTS]: funcs.listReports,
  • src/toolkit.ts:70-936 (registration)
    Dynamic registration of all tools including list_reports in the MCP server (PaddleMCPServer), using the schema from tools.ts and delegating execution to PaddleAPI.run.
            tool.method,
            tool.description,
            tool.parameters.shape,
            annotations,
            async (arg: unknown, _extra: unknown) => {
              const result = await this._paddle.run(tool.method, arg);
              return {
                content: [
                  {
                    type: "text" as const,
                    text: String(result),
                  },
                ],
              };
            },
          );
    
          registeredCount++;
        });
    
        if (registeredCount === 0) {
          throw new Error(
            "No tools were registered with the current filter settings. " +
            "The value of the --tools parameter must be 'all', 'read-only', 'non-destructive', or a comma-separated list of valid tools."
          );
        }
      }
    }
    
    export default PaddleMCPServer;
  • Constant definition for the LIST_REPORTS tool method string used in registrations and mappings.
    LIST_REPORTS: "list_reports",
Behavior4/5

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

Annotations provide readOnlyHint=true, and the description adds valuable behavioral context beyond that: it specifies pagination behavior ('Results are paginated'), recommends default usage ('Use the maximum perPage by default'), and notes currency formatting ('Amounts are in the smallest currency unit'). This enhances understanding without contradicting annotations.

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?

The description is appropriately sized and front-loaded with the core purpose. Each sentence adds value: purpose, default behavior, filtering, pagination, sorting, and currency details. There's minimal waste, though it could be slightly more structured for clarity.

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 the tool's moderate complexity, 4 parameters with full schema coverage, readOnlyHint annotation, and no output schema, the description is reasonably complete. It covers key behavioral aspects like pagination and currency units, though it could benefit from more explicit sibling differentiation or error handling details.

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?

With 100% schema description coverage, the baseline is 3. The description adds some semantic context (e.g., explaining pagination with 'after' and recommending 'perPage' defaults), but doesn't provide significant additional meaning beyond what the schema already documents for each parameter.

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 the tool's purpose: 'list reports in Paddle'. It specifies the verb ('list') and resource ('reports'), and while it doesn't explicitly differentiate from siblings like 'get_report' or 'create_report', the listing nature is evident. However, it doesn't fully distinguish from other list_* tools in the context.

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 description provides implied usage guidance through parameter explanations (e.g., 'Filter reports by status as needed'), but doesn't explicitly state when to use this tool versus alternatives like 'get_report' for individual reports or 'create_report' for new ones. It offers some context but lacks clear when/when-not directives.

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/PaddleHQ/paddle-mcp-server'

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