Skip to main content
Glama

fields_create_product_field

Create custom fields for products like dropdowns, text, or numeric fields to store additional product data in Pipedrive.

Instructions

Create a new custom field for products.

For enum and set field types, you must provide options (a non-empty array of { label } objects).

Common use cases:

  • Add a "Product Category" dropdown to products

  • Add a custom text field (e.g., "SKU Code")

  • Add a numeric field (e.g., "Weight (kg)")

After creation, the field's key is the hash you must use in Product create/update payloads. Field definitions are cached for 15 minutes — call fields_list_product_fields after a brief delay to see it reflected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name of the field
optionsNoRequired for `enum` and `set` field types
field_typeYesType of the field. `enum`/`set` require `options`.
add_visible_flagNoWhether the field is shown in the "add" form by default
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses the 15-minute cache, the need to use the field's key in product payloads, and option requirements. This is sufficient for a creation tool.

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 well-structured: first sentence states purpose, then parameter-specific notes, then use cases, then post-creation behavior. Every sentence adds value, and it is front-loaded with the key action.

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?

Given the tool has 4 parameters, 100% schema coverage, no output schema, and no annotations, the description covers creation requirements, caching, and verification steps. It is complete enough for an agent to use correctly, though return value is not specified (acceptable for a creation tool).

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 coverage is 100%, so baseline is 3. The description adds value by explaining the options requirement for enum/set, providing use case examples, and noting the field's key usage after creation. This justifies a 4.

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 clearly states 'Create a new custom field for products.' This specific verb+resource+scope distinguishes it from sibling tools like fields_create_deal_field, as it targets product fields.

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 provides common use cases, requirements for enum/set types, and mentions the caching delay with the need to call fields_list_product_fields to verify. It does not explicitly exclude alternatives but gives clear context for when 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/nubiia-dev/mcp-pipedrive'

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