Skip to main content
Glama
MSPbotsAI

chargebee-mcp

by MSPbotsAI

chargebee_update_customer

Update an existing Chargebee customer's profile with new contact details, company info, taxability, and payment settings.

Instructions

Update a customer (company).

    API: POST /customers/{customer-id}

    Args:
        customer_id: The customer's unique ID.
        first_name: Customer's first name.
        last_name: Customer's last name.
        email: Customer's email address.
        company: Company name.
        phone: Phone number.
        auto_collection: "on" or "off".
        taxability: "taxable" or "exempt".
        locale: Customer's locale.
        invoice_notes: Default notes shown on the customer's invoices.
        meta_data: Arbitrary key-value metadata dict.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
phoneNo
localeNo
companyNo
last_nameNo
meta_dataNo
first_nameNo
taxabilityNo
customer_idYes
invoice_notesNo
auto_collectionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are present, so the description must disclose behavioral details. It provides the API method and endpoint but does not explain whether the update is partial or full, idempotency, permission requirements, or potential side effects. This leaves significant behavioral ambiguity.

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 docstring-style layout is efficient for 11 parameters, starting with the core purpose and API endpoint. It avoids unnecessary fluff but is somewhat formulaic in repeating each argument on its own line; still appropriately sized.

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

Completeness3/5

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

The description covers all parameters and the endpoint, but lacks behavioral context such as update semantics, usage guidelines, and any caveats. With an output schema present, return values are not needed, but the missing behavioral and usage guidance leaves the tool only partially complete.

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?

Every parameter receives a concise semantic definition in the description, far exceeding the bare schema types. It adds concrete meaning such as allowed values for auto_collection and taxability, and the purpose of invoice_notes and meta_data, which the schema lacks entirely.

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 'Update a customer' and specifies the API endpoint, making the action unambiguous. It distinguishes from sibling tools like retrieve, list, and create by focusing on modification.

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?

Usage is implied from 'Update a customer,' but no explicit guidance is given on when to use this tool versus alternatives, nor are exclusions or prerequisites mentioned. The context of modifying an existing customer is understood but not spelled out.

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