Skip to main content
Glama
MSPbotsAI

chargebee-mcp

by MSPbotsAI

chargebee_list_subscriptions

Retrieve subscriptions from Chargebee with optional filters, pagination, and inclusion of deleted records. Use to fetch matching subscription data via the Chargebee REST API.

Instructions

List subscriptions (accounts).

    API: GET /subscriptions

    Args:
        limit: Max results per page (1-100, default 10).
        offset: Pagination cursor from a previous response's next_offset.
        include_deleted: Include deleted subscriptions in the results.
        filters: Optional Chargebee compound filter fields, passed through
            as literal query keys, e.g. {"customer_id[is]": "cus123",
            "status[in]": "[\"active\",\"non_renewing\"]"}. Supported
            fields: id, customer_id, item_id, item_price_id, status,
            cancel_reason, cancel_reason_code, remaining_billing_cycles,
            created_at, activated_at, next_billing_at, cancelled_at,
            has_scheduled_changes, updated_at, offline_payment_method,
            auto_close_invoices, override_relationship,
            business_entity_id, channel, decommissioned. 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
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: pagination via limit and offset, include_deleted flag, and a thorough explanation of filters including supported fields and operators. It also mentions the API endpoint. This is a high level of transparency for a read operation.

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-organized: a concise purpose line, the API endpoint, then each argument with clear formatting. The filter details are lengthy but necessary, and there is no redundancy. Every sentence contributes useful information.

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?

The tool has 4 optional parameters including a complex filter object, and no annotations. The description covers all invocation needs, including parameter semantics and behavior. An output schema exists, so return values are not required in the description. The only minor gap is usage guidance, already scored separately.

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 coverage is 0%, but the description adds substantial meaning to each parameter: limit's range and default, offset as a pagination cursor from next_offset, include_deleted's effect, and filters with examples and detailed supported fields/operators. This goes far beyond the basic schema types.

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 subscriptions (accounts).' with a specific verb and resource. It distinguishes from siblings like retrieve_subscription (singular) and cancel_subscription by indicating a listing operation for multiple subscriptions.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as retrieve_subscription or cancel_subscription. It mentions no prerequisites, exclusions, or comparison with other tools, relying solely on the implied purpose.

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