Skip to main content
Glama

update_customer

Update an existing customer's details such as name, email, status, or tax exemption. Requires customer ID, with optional fields for personal and billing information.

Instructions

Update an existing customer. PUT /customers/{customerId}. Required: customerId. Optional: firstName, lastName, email, businessName, locale, phoneNum, phoneExt, preferredCurrency, taxExempt, status (active|disabled|archived).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesCustomer ID to update (required)
firstNameNoCustomer first name
lastNameNoCustomer last name
emailNoCustomer email
businessNameNoBusiness name
localeNoLocale code
phoneNumNoPhone number
phoneExtNoPhone extension
preferredCurrencyNoPreferred currency code
taxExemptNoWhether customer is tax exempt
statusNoCustomer status: active, disabled, or archived
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It mentions the PUT method and lists fields but does not clarify whether omitted optional fields are preserved or cleared, nor does it discuss side effects, idempotency, or permissions.

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 a single sentence that efficiently conveys purpose and required/optional fields. It is front-loaded and avoids unnecessary words, though structured formatting could improve readability.

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?

For a mutation tool with 11 parameters and no output schema, the description covers purpose and field requirements but lacks details about return values, error handling, and behavioral semantics (e.g., partial vs full update).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, and the description essentially repeats the schema's parameter list. It adds minimal new meaning beyond what the schema already provides.

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 the action ('Update an existing customer') and specifies the HTTP method and endpoint. Distinguishes from sibling tools like create_customer and delete_customer.

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?

Lists required and optional fields, providing direct guidance on what to include. However, it does not explicitly contrast with alternatives (e.g., create_customer for new customers) or mention when not to use this tool.

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/rhinosaas/rebillia-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server