pax8-mcp

Overview Schema Source Related Servers Discussions Admin

pax8_list_subscriptions

List subscriptions from the Pax8 partner account with filters for company, status, product, and pagination to get the exact data you need.

Instructions

List subscriptions in the Pax8 partner account.

    Args:
        page: Zero-based page number for pagination (default: 0).
        size: Number of results per page (default: 10).
        sort: Sort field and direction, e.g. "startDate,asc".
        company_id: Filter by company ID.
        status: Filter by subscription status. One of: Active, Cancelled,
            PendingManual, PendingAutomated, PendingCancel, Terminated, Expired, Trial.
        product_id: Filter by product ID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`size`	No
`sort`	No
`status`	No
`company_id`	No
`product_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of explaining behavior. It lists the basic function and parameters, but does not disclose pagination behavior, sort format details (beyond an example), or potential errors, leaving some behavioral aspects unclear.

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 concise and well-structured, with a single introductory sentence followed by a clear parameter list. No unnecessary information is included.

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 simplicity and the presence of an output schema, the description is nearly complete. It could add a note about default pagination or listing behavior, but the core use case is fully covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description text provides a clear explanation for every parameter (page, size, sort, company_id, status, product_id), including valid status values and an example for sort. This adds significant meaning beyond the schema titles and defaults.

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?

The description clearly states the tool lists subscriptions within the Pax8 partner account, using a specific verb and resource. It is easily distinguishable from sibling tools that list companies, invoices, products, etc.

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

Usage Guidelines4/5

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

The description provides no explicit usage guidance, but the resource type (subscriptions) and available filters make it obvious when to use this tool versus siblings. It could improve by mentioning that it is the appropriate choice for subscription-related queries.

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

Deploy Server