Skip to main content
Glama
MSPbotsAI

chargebee-mcp

by MSPbotsAI

chargebee_list_transactions

Retrieve payment and refund transactions with optional filters for customer, subscription, date, amount, status, and more. Supports pagination and deleted records.

Instructions

List payment/refund transactions.

    API: GET /transactions

    Args:
        limit: Max results per page (1-100, default 10).
        offset: Pagination cursor from a previous response's next_offset.
        include_deleted: Include deleted transactions in the results.
        filters: Optional Chargebee compound filter fields, passed through
            as literal query keys, e.g. {"customer_id[is]": "cus123",
            "type[is]": "payment", "date[after]": "1700000000"}. Supported
            fields: id, customer_id, subscription_id, payment_source_id,
            payment_method, gateway, gateway_account_id, id_at_gateway,
            reference_number, type, date, amount, amount_capturable,
            status, updated_at. Supported operators vary by field type:
            [is], [is_not], [in], [not_in], [between], [after], [before],
            [on], [none], [is_present].
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
filtersNo
include_deletedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the burden and discloses the API endpoint, pagination via offset and next_offset, the option to include deleted transactions, and detailed filter semantics. This goes beyond a simple 'list' and provides expectations around read-only behavior and pagination.

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 well-structured with a one-sentence summary, API endpoint, and a clear Args list. Every sentence provides necessary detail, especially for the complex filter syntax, without redundancy. It is appropriately front-loaded.

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

Completeness5/5

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

Despite the complexity, the description covers all necessary aspects: pagination behavior, filtering fields and operators, inclusion of deleted records, and param defaults. An output schema exists, so return values are documented externally. The description fully supports invocation without missing crucial information.

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?

Schema description coverage is 0%, but the description comprehensively explains each parameter: limit with range and default, offset as a cursor, include_deleted as a boolean, and filters with supported field types and operators. The filters section adds substantial meaning beyond the schema's bare property definitions.

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 states 'List payment/refund transactions' with a specific verb and resource, clearly distinguishing it from sibling tools that list customers, subscriptions, or invoices. It also specifies the API endpoint, reinforcing the action.

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 implies usage when a list of transactions is needed, but it does not explicitly provide guidance on when to use this tool versus alternatives like chargebee_list_invoices. No when-not-to-use or alternative tooling is mentioned.

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/MSPbotsAI/chargebee-mcp'

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