Skip to main content
Glama
MSPbotsAI

chargebee-mcp

by MSPbotsAI

chargebee_create_customer

Create a customer (individual or company) in Chargebee by submitting contact, billing, tax, and payment preferences.

Instructions

Create a customer (company).

    API: POST /customers

    Args:
        first_name: Customer's first name.
        last_name: Customer's last name.
        email: Customer's email address.
        company: Company name.
        phone: Phone number.
        id: Optional custom customer ID (auto-generated if omitted).
        auto_collection: "on" or "off" — whether invoices are auto-collected.
        taxability: "taxable" or "exempt".
        locale: Customer's locale (e.g. "en", "fr-CA").
        meta_data: Arbitrary key-value metadata dict.
        billing_address: Billing address fields, e.g. {"line1": "...",
            "city": "...", "state": "...", "zip": "...", "country": "US"}.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
emailNo
phoneNo
localeNo
companyNo
last_nameNo
meta_dataNo
first_nameNo
taxabilityNo
auto_collectionNo
billing_addressNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the API endpoint, auto-generated id behavior, and allowed values for auto_collection/taxability, but does not mention permissions, error handling, or side effects beyond creation.

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?

Concise docstring with front-loaded purpose, API line, and one line per parameter. Every sentence adds value; no redundancy.

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?

Covers all parameters and provides the API endpoint, but lacks usage guidance and behavioral details like auth or idempotency. Since an output schema exists, return values are not required, making it mostly complete for its complexity.

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%, and the description compensates by defining all 11 parameters, including allowed values for auto_collection and taxability, an example for billing_address, and the optional/auto-generated behavior of id.

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?

Clearly states 'Create a customer (company)' with a specific verb and resource. The API endpoint 'POST /customers' reinforces the action, and the tool is distinct from sibling tools like retrieve/update/list.

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 vs alternatives, but the verb 'Create' implies the use case for new customer creation. No exclusions or alternative recommendations are provided.

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