Skip to main content
Glama
MSPbotsAI

chargebee-mcp

by MSPbotsAI

chargebee_list_invoices

List invoices from Chargebee using filters for customer, status, date, or amount. Supports pagination and including deleted records.

Instructions

List invoices.

    API: GET /invoices

    Args:
        limit: Max results per page (1-100, default 10).
        offset: Pagination cursor from a previous response's next_offset.
        include_deleted: Include deleted invoices in the results.
        filters: Optional Chargebee compound filter fields, passed through
            as literal query keys, e.g. {"customer_id[is]": "cus123",
            "status[in]": "[\"paid\",\"payment_due\"]",
            "date[after]": "1700000000"}. Supported fields: id,
            subscription_id, customer_id, recurring, status, price_type,
            date, paid_at, total, amount_paid, amount_adjusted,
            credits_applied, amount_due, dunning_status, payment_owner,
            updated_at, channel, voided_at, void_reason_code, exclude,
            einvoice. 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 full burden. It details pagination via limit and offset, includes include_deleted behavior, and thoroughly explains the filter syntax including supported fields and operators. It does not mention rate limits or authorization, but for a read-only list operation, the disclosed behavior is substantial and non-contradictory.

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 well-structured: a one-line purpose, the endpoint, then a bulleted Args list. The filter details are lengthy but necessary for correct usage. It is front-loaded with the core 'List invoices' statement. Minor redundancy with the schema (e.g., limit default) is acceptable given the low schema coverage.

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?

Given the tool's complexity (filtering with many fields/operators), the description fully covers all parameters, pagination mechanics, and filter behavior. An output schema exists, so return-value details are not required. The description is sufficient for an agent to invoke the tool correctly with minimal missing context.

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%, so the description must compensate—it does. Each parameter (limit, offset, include_deleted, filters) is explicitly described with defaults, types, and even a JSON example for filters. The filter field and operator lists provide far more meaning than the bare schema properties, which only specify types 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 opens with 'List invoices'—a specific verb and resource. It clearly distinguishes from sibling tools like list_subscriptions and list_transactions by naming invoices as the target. The API endpoint reinforces the purpose without ambiguity.

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 does not explicitly state when to use this tool over alternatives, nor does it mention exclusions or sibling tools. It implies usage through the resource name, but lacks direct guidance like 'Use this for invoice history' or 'For transactions, use chargebee_list_transactions.' This is a neutral, minimal usage signal.

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