Skip to main content
Glama
zenskar

Zenskar MCP Server

Official
by zenskar

updateCustomer

updateCustomer

Partially update a customer's details including name, email, address, phone, tax info, and billing settings. Only send fields to change.

Instructions

Update an existing customer's details. Supports partial updates — only send fields you want to change. Can update name, email, address, phone, communications_enabled, auto_charge_enabled, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesThe unique identifier (UUID) of the customer to update.
customer_nameNoUpdated customer name.
emailNoUpdated email address.
phone_numberNoUpdated phone number.
external_idNoUpdated external identifier.
address_line1NoAddress line 1.
address_line2NoAddress line 2.
address_cityNoCity.
address_stateNoState.
address_zipCodeNoZIP/postal code.
address_countryNoCountry.
address_country_codeNoCountry code (e.g. US, GB).
communications_enabledNoEnable/disable invoice email communications.
auto_charge_enabledNoEnable/disable auto-charge for this customer.
business_entity_idNoUUID of the business entity to associate with.
address_line3NoAddress line 3.
ship_to_line1NoShipping address line 1.
ship_to_line2NoShipping address line 2.
ship_to_line3NoShipping address line 3.
ship_to_cityNoShipping address city.
ship_to_stateNoShipping address state.
ship_to_zipCodeNoShipping address ZIP/postal code.
ship_to_countryNoShipping address country.
ship_to_country_codeNoShipping address country code (e.g. US, GB).
custom_dataNoCustom key-value pairs for additional customer info (e.g., {"industry": "saas", "account_tier": "enterprise"}).
tax_infoNoList of tax identifiers. Each item: {country_code, tax_code, tax_id}. country_code uses mixed ISO formats (e.g. 'USA', 'IND', 'AUS', 'EU', 'GB'/'UK', 'SG', 'JP', 'BR', 'CA', and 2-letter codes for EU members like 'DE', 'FR', 'IT'). tax_code varies by country — common pairings: VAT (most of EU + UK + CH + most of MENA + IL/PH/ZA/EG/JO etc.), GST (India, Australia, Singapore), GST/HST (Canada), GST/IRD (NZ), TIN (USA, Qatar, Kuwait, Iraq, Libya), JCT (Japan), CNPJ (Brazil), SST (Malaysia), NPWP (Indonesia), MVA (Norway). Pair country_code + tax_code correctly.
__userContextNoInternal user context for multi-tenant authentication and approval workflow
Behavior2/5

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

No annotations provided, so description carries full burden. It only states the update capability and partial update support, but omits important behavioral traits like permission requirements, error handling, or response format. For a tool with 27 parameters, this is insufficient.

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?

Two sentences, front-loaded with the main action, no superfluous words. Ideal length and structure.

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

Completeness2/5

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

Given the complexity (27 parameters, nested objects like tax_info and custom_data), the description lacks detail on return values, validation rules, and special parameter usage. The 'etc.' is vague, making it incomplete for an agent to reliably use.

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?

Schema description coverage is 100%, so baseline is 3. The description adds marginal value by listing some fields and emphasizing partial updates, but does not provide new meaning beyond the schema definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Update an existing customer's details' with specific verb and resource, and lists updatable fields. However, it does not explicitly differentiate from sibling tools like updateCustomerAddress or createCustomer.

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?

Explicitly mentions 'Supports partial updates — only send fields you want to change', which provides clear context for usage. But lacks guidance on when not to use this tool vs alternatives like updateCustomerAddress.

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/zenskar/mcp-zenskar'

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