Skip to main content
Glama
ckalima

Pipedrive MCP Server

pipedrive_create_product_field

Create a custom product field in Pipedrive by specifying field name and type. For enum or set types, include options. The response provides a field code for later updates.

Instructions

Create a product custom field. field_name and field_type are required. For enum/set types, options is required. Product fields use a simpler model: no description, important_fields, or required_fields. The response data.field_code is the 40-char hash to keep for later updates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
field_nameYesField name (required, 1-255 chars)
field_typeYesField type. Use 'enum' (single choice) or 'set' (multiple choice) for option fields.
optionsNoField options (required for enum and set field types)
ui_visibilityNoUI visibility (product fields use a simpler model): add_visible_flag, details_visible_flag.
Behavior4/5

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

The description adds meaningful behavioral details beyond annotations: it clarifies required fields, conditional options for enum/set types, the simpler model for product fields, and the importance of the response field_code. Annotations are consistent with the create operation.

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?

The description is short and front-loaded with the main purpose. It efficiently conveys key points without unnecessary fluff, though minor restructuring could improve readability.

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?

For a create tool with no output schema, the description explains the response field and constraints. It covers all required aspects, but lacks information on errors or side effects.

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 the baseline is 3. The description reinforces the requirements and adds nuance about ui_visibility having a simpler model, but does not significantly enhance understanding beyond the schema.

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?

The description clearly states the tool creates a product custom field and specifies required parameters. However, it does not differentiate from sibling tools like pipedrive_create_deal_field or pipedrive_create_organization_field, leaving ambiguity about when to use this specific tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide explicit guidance on when to use this tool versus alternatives. It lacks context on prerequisites, limitations, or exclusive use cases, which is a significant gap given the number of sibling field creation tools.

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/ckalima/pipedrive-mcp-server'

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