Skip to main content
Glama

fields_create_project_field

Create custom fields for projects by specifying a name, field type, and optional options for enum or set fields. Returns a field_code for future updates or deletions.

Instructions

Create a new custom field for projects (API v2).

For enum and set field types you must provide options (a non-empty array of { label } objects). The created field's field_code is what you use to update or delete it later.

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`.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the dependency on options for enum/set types and the reuse of field_code for future operations. It does not mention auth or rate limits, but for a creation tool this is adequate behavior disclosure.

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?

Two sentences: first states purpose, second adds essential usage detail. Front-loaded, no redundancy, every clause earns its place.

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 exists, so description should imply return structure. Mentioning field_code hints at the response containing it. The tool's simplicity (3 params, 2 required) means minimal expectations; completeness is adequate for a basic 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% (all 3 parameters described). The description adds behavioral context beyond schema: options must be non-empty label arrays for enum/set, and field_code is used for updates. This enhances understanding of how parameters relate to tool behavior.

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 the verb 'Create' and the resource 'new custom field for projects (API v2)', distinguishing it from sibling tools like fields_create_deal_field. The resource scope is explicitly 'for projects', making the purpose unambiguous.

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 specific usage guidelines: enum/set fields require options with label objects, and the resulting field_code is used for later updates/deletes. It does not explicitly state when to use vs alternatives, but the naming convention with siblings (project vs deal vs person) makes it obvious.

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