Skip to main content
Glama

fields_update_person_field

Update custom person fields by renaming, managing dropdown options, or toggling add form visibility.

Instructions

Update an existing custom person field.

Note: field_type cannot be changed. For enum/set fields, options is the full set of options after update — include each existing option's id to preserve it, or omit id to add a new option.

Common use cases:

  • Rename a field

  • Add/remove options on an enum dropdown

  • Toggle the field's visibility in the add form

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the person field to update
nameNoNew display name of the field
optionsNoNew full set of options. Include existing `id` to preserve, omit it to add.
add_visible_flagNoWhether the field is shown in the "add" form by default
Behavior3/5

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

No annotations provided, so the description carries the full burden. It notes that `field_type` cannot be changed and that options must be the full set, which adds behavioral context beyond the schema. However, it does not disclose authorization requirements, side effects, or what happens to unchanged fields. Moderate transparency.

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 concise, with a clear main line and a note section. Bullet points for common use cases help readability. Could be slightly more structured, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description does not mention the response format or any error conditions. For a mutation tool, it lacks information on what the API returns after update, which is needed for an agent to use it correctly. The description covers use cases but not the full context.

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%, baseline 3. The description adds value by explaining the semantics of the `options` parameter (full set, use of `id` to preserve), which is not fully clear from the schema alone. It also ties parameters to use cases, improving meaning.

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 it updates an existing custom person field. The verb 'update' and resource 'person field' are specific. While the name distinguishes it from sibling field update tools, the description does not explicitly contrast them, so it's not a perfect 5.

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

Usage Guidelines3/5

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

The description provides common use cases (rename, add/remove options, toggle visibility) and a note on options semantics. However, it does not specify when not to use this tool or mention alternatives for updating other field types. Usage context is implied but not exhaustive.

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