Skip to main content
Glama

fields_create_organization_field

Add custom fields to organizations in Pipedrive, such as dropdowns, monetary values, or dates, to capture specific business data.

Instructions

Create a new custom field for organizations.

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

Common use cases:

  • Add a "Customer Type" dropdown to organizations

  • Add a custom monetary value (e.g., "Annual Revenue")

  • Add a date field (e.g., "Customer Since")

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name of the field
field_typeYesType of the field. `enum`/`set` require `options`.
optionsNoRequired for `enum` and `set` field types
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 provided, but the description discloses key behaviors: caching for 15 minutes, that the field key is a hash used in other payloads, and required options for enum/set. It does not mention permissions, error handling, or maximum lengths, but for a create tool, this is adequate.

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 concise and well-structured: purpose, constraints, use cases, and post-creation behavior are clearly separated. Every sentence adds necessary information without redundancy.

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's complexity (4 parameters, 2 required, no output schema) and the provided sibling context, the description covers all essential aspects: required inputs, behavioral nuances (caching, key usage), and typical scenarios. It does not explain return values but that is 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?

With 100% schema coverage, the baseline is 3. The description adds value by explaining the options parameter requirement for enum/set, providing use case examples for different field types, and linking the result to the key used in other operations. This goes beyond the schema definitions.

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 first sentence clearly states the tool creates a new custom field for organizations. Examples of use cases further clarify the purpose, and it is easily distinguishable from sibling tools like fields_delete_organization_field or fields_list_organization_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 context on when to use this tool by listing common use cases and specifying constraints for enum/set types. It also suggests calling fields_list_organization_fields after a delay to see results. However, it does not explicitly compare to alternatives like fields_update_organization_field or give 'when not to use' guidance.

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

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