Skip to main content
Glama

fields_create_deal_field

Create custom fields for deals to capture specific data like dropdowns, monetary values, or dates. Specify field name, type, and option labels for enum/set fields.

Instructions

Create a new custom field for deals.

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

Common use cases:

  • Add a "Deal Source" dropdown to deals

  • Add a custom monetary value (e.g., "Expected Upsell")

  • Add a date field (e.g., "Contract Start Date")

After creation, the field's key is the hash you must use in Deal create/update payloads. Field definitions are cached for 15 minutes — call fields_list_deal_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 provided, so description must bear full burden. Reveals that after creation, the field's key is the hash for payloads. Also discloses 15-minute cache delay. These are important behavioral traits that go beyond the schema.

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?

Description is concise, well-structured: starts with main purpose, then specific requirements, common use cases, and post-creation behavior. No unnecessary words; each sentence adds value.

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?

No output schema or annotations, but description covers creation flow: requirements, use cases, and post-creation (key, caching). Could mention error conditions or permissions, but for a straightforward creation tool, it is sufficiently complete.

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% with descriptions for all 4 parameters. Description adds value by explaining the options format ({ label } objects) and the consequence of creation (key usage). This enhances understanding 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 clearly states 'Create a new custom field for deals' with specific verb and resource. It provides common use cases (dropdown, monetary, date) which reinforces the purpose. Differentiates from sibling tools like fields_create_organization_field by specifying 'deals'.

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?

Explicitly states requirement for enum/set types to provide options. Provides common use cases as guidance. Mentions caching delay and need to call fields_list_deal_fields to see reflection. Lacks explicit alternatives, but domain distinction with siblings is clear.

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