Skip to main content
Glama

create_customer_property

Create a workspace-wide custom field for customer records. Define its type, required status, default value, and visibility to capture tailored customer data.

Instructions

Create a customer property (a workspace-wide custom field on customers).

property_type, is_multi and settings are fixed once created — recreate the property to change them.

Args: name: Required, but discarded — the stored name is a slug of display_name. Pass display_name here too if you have nothing else. display_name: User-facing label. Must be unique in the workspace: it derives the property's slug, so a display name already in use is rejected. property_type: TEXT | DATETIME | DECIMAL | BOOLEAN | OPTION | RELATION | URL | EMAIL | FILE relation_type: ISSUE | USER — required when property_type=RELATION description: Property description is_required: Whether a value must be set; forces default_value to be empty default_value: Default value(s); at most one unless is_multi settings: Required for TEXT/DATETIME. TEXT: {"display_format": "single-line"|"multi-line"|"readonly"} DATETIME: {"display_format": "MMM dd, yyyy"|"dd/MM/yyyy"|"MM/dd/yyyy"|"yyyy/MM/dd"} is_active: Whether the property is active is_multi: Whether the property holds multiple values options: For OPTION type — [{"name": str, "description"?: str, "is_default"?: bool}] external_source: External system this property came from, e.g. "salesforce" external_id: The property's ID in that external system

Returns: The created CustomerProperty, including its options for OPTION type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
optionsNo
is_multiNo
settingsNo
is_activeNo
descriptionNo
external_idNo
is_requiredNo
display_nameYes
default_valueNo
property_typeYes
relation_typeNo
external_sourceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
optionsNo
is_multiNo
settingsNo
is_activeNo
workspaceNo
created_atNo
created_byNo
deleted_atNo
logo_propsNo
sort_orderNo
updated_atNo
updated_byNo
descriptionNo
external_idNo
is_requiredNo
display_nameYes
default_valueNo
property_typeYes
relation_typeNo
external_sourceNo
validation_rulesNo
Behavior5/5

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

With no annotations, the description fully carries the behavioral transparency burden. It discloses immutability of key fields, the discarded 'name' argument, uniqueness constraints on display_name, interdependence of is_required and default_value, and conditional requirements for settings and relation_type.

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?

The description is long but tightly organized with 'Args' and 'Returns' sections, with each parameter on its own line and inline format hints. Every sentence adds necessary detail; nothing is redundant or filler.

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

Completeness5/5

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

Given 13 parameters, 0% schema coverage, and no annotations, the description provides comprehensive information: all parameter meanings, constraints, defaults, and return value. It fully equips an agent to invoke the tool correctly.

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?

Schema description coverage is 0%, and the description compensates admirably by explaining every parameter's purpose, constraints, and expected format. It provides examples for settings and options, which the bare schema does not offer.

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 states a specific verb ('Create') and resource ('customer property'), clarifying it as a workspace-wide custom field on customers. This clearly distinguishes it from sibling tools like create_work_item_property or create_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?

The description's opening parenthetical clearly defines the tool's domain (workspace-wide customer fields), which helps an agent select it over work-item property tools. However, it does not explicitly mention when not to use it or point to alternatives, though the context is sufficient.

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/leigangzhang/plane-mcp-server-adapter'

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