Skip to main content
Glama
PedroHSGuimaraes

Tienda Nube MCP Server

tiendanube_create_customer

Create a customer account with required name and email, and optional details like address, phone, identification, and notes. Use for registration, imports, or integration.

Instructions

➕ CREATE NEW CUSTOMER - Create a new customer account with complete profile information. Use this for customer registration, manual account creation, bulk imports, or integrating with external systems. Requires name and email as minimum fields. Supports phone, identification documents, addresses, notes, passwords, and email invitation sending. Ideal for onboarding and customer management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCustomer full name (required)
emailYesCustomer email address (required)
passwordNoCustomer password. If not provided, an invitation email will be sent.
send_invitationNoSend an invitation email to the customer to create a password.
phoneNoCustomer phone number
identificationNoCustomer identification/document number
noteNoInternal notes about the customer
addressNoCustomer address street
cityNoCustomer city
provinceNoCustomer province/state
countryNoCustomer country
zipcodeNoCustomer ZIP/postal code
numberNoAddress number
floorNoAddress floor/apartment
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 notes required fields and optional parameters but does not explain side effects, success/failure behavior, or return values. The mention of password and invitation is helpful but incomplete.

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?

Two sentences with a clear heading emoji. Information is front-loaded and focused. Could be slightly more structured but remains efficient and readable.

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?

With 14 parameters and no output schema or annotations, the description should cover return value, uniqueness, error conditions, and behavior more thoroughly. It omits important context like what the response contains or potential failures, leaving the agent with gaps.

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 coverage is 100%, so baseline is 3. The description adds minimal extra value, grouping parameters by type (phone, identification, addresses, etc.) and clarifying the password/invitation interaction. It does not provide new semantic details beyond the schema.

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 explicitly states 'CREATE NEW CUSTOMER' and details use cases like registration, manual creation, bulk imports, and system integration. It clearly distinguishes from sibling tools (update, search, get, list) by focusing on creation.

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 lists appropriate use cases but does not specify when not to use it or mention alternatives like update or search. It lacks explicit exclusions or decision heuristics.

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/PedroHSGuimaraes/nuvem-shop-mcp-server'

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