Skip to main content
Glama

update_customer

Update customer basic information such as name, email, phone, gender, or birthday. Only provided fields are modified, leaving others unchanged.

Instructions

[WRITE] 更新客戶基本資料。

【用途】 修改客戶姓名、聯絡方式、生日等基本資料。僅傳入要修改的欄位,未傳入的欄位不會被覆蓋。

【呼叫的 Shopline API】

  • PUT /v1/customers/{customer_id}

【回傳結構】 dict 含 success: bool, resource_id: str, message: str。

【副作用】

  • 修改客戶資料,變更立即生效

  • 不可復原(無版本歷史),但可再次呼叫此工具覆蓋

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes客戶內部 ID
nameNo新姓名
emailNo新 Email
phoneNo新電話
genderNo性別 (male/female/other)
birthdayNo生日 YYYY-MM-DD
Behavior4/5

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

Discloses mutation behavior (WRITE), immediate effect, irreversibility (no version history), and ability to overwrite. With no annotations, this carries the full burden and does so well.

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?

Well-structured with clear sections (type, purpose, API call, return structure, side effects). Each sentence is informative and concise, with no wasted words.

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 purpose, usage, API endpoint, return structure, and side effects. Lacks error scenarios but is sufficient for a mutation tool without output schema.

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

Parameters4/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 valuable guidance on partial update semantics (only modify passed fields), which goes beyond schema descriptions.

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 it updates customer basic information (name, contact, birthday) and specifies the HTTP method and endpoint. Distinguishes from sibling tools like create_customer, delete_customer, and update_customer_tags.

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?

Explicitly states that only passed fields are updated and omitted fields are not overwritten. Provides context for usage but does not explicitly compare to other customer-update siblings.

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/asgard-ai-platform/mcp-shopline'

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