Skip to main content
Glama
MSPbotsAI

chargebee-mcp

by MSPbotsAI

chargebee_list_customers

List Chargebee customers with pagination, include deleted records, and filter by fields such as email, company, or creation date.

Instructions

List customers (companies).

    API: GET /customers

    Args:
        limit: Max results per page (1-100, default 10).
        offset: Pagination cursor from a previous response's next_offset.
        include_deleted: Include deleted customers in the results.
        filters: Optional Chargebee compound filter fields, passed through
            as literal query keys, e.g. {"email[is]": "a@b.com",
            "company[is]": "Acme", "created_at[after]": "1700000000"}.
            Supported fields: id, first_name, last_name, email, company,
            phone, auto_collection, taxability, created_at, updated_at,
            offline_payment_method, auto_close_invoices, channel,
            business_entity_id, relationship. Supported operators vary by
            field type: [is], [is_not], [starts_with], [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
Behavior5/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It thoroughly explains pagination via offset, the include_deleted flag, and the complex filter syntax including supported fields and operators. This provides substantial behavioral transparency beyond the basic 'list' semantics, and it is clearly a read-only operation.

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 structured and front-loaded with the core purpose, followed by parameter explanations. While lengthy, every section is necessary to document the flexible filtering and pagination. It could be slightly condensed, but it remains efficient.

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 and the presence of an output schema, the description covers all necessary usage aspects: API endpoint, pagination, filtering fields and operators. It does not need to document return values because the output schema exists. The description is complete for an agent to invoke the tool correctly.

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 schema has zero descriptions, so the description must compensate. It does so effectively by explaining limit's range and default, offset as a pagination cursor, include_deleted, and the entire filter structure with examples and supported operators. This adds significant meaning beyond the raw schema.

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 'List customers (companies)' with the API endpoint GET /customers. This distinguishes it from sibling tools like retrieve/create/update customers, and specifies that customers are companies.

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 clear context for when to use this tool: it is the list operation for customers, with pagination and filtering options. It does not explicitly mention alternatives or exclusions, but the sibling tools are distinct (retrieve, create, update), so the usage is evident.

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