Skip to main content
Glama
gray-wilbee

fub-mcp

by gray-wilbee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_deal_custom_field

Update a deal's custom field by ID, changing its label, type, dropdown choices, order, or read-only settings.

Instructions

Update a deals custom field. (PUT /dealCustomFields/{id})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
typeYesThe type of deals custom field.
labelYesThe user-friendly name of the custom field (e.g., "Anniversary").
choicesNoArray of options related to a deals custom field of type `Dropdown`.
readOnlyNoSets whether the field is read only or not.
extraBodyNoExtra raw JSON body fields not explicitly listed above — e.g. custom.* fields when creating/updating people or deals. Keys and values are sent as-is.
extraQueryNoExtra raw query parameters not explicitly listed above — e.g. FUB custom field filters like custom.ClosingDate on /people or /deals. Keys and values are sent as-is.
hideIfEmptyNoSets whether we will hide this field if it is empty.
isRecurringNoWhether a date field occurs every year (e.g. birthdays, anniversaries, etc.).
orderWeightNoA weighted integer for the field to assign values for custom sorting.
dropdownChoiceMapNoAn optional mapping that points previous dropdown choices (keys) to their new positions (values). This is used to track when options get moved or renamed. If items are missing from the keys, they will be removed. If the mapping is not supplied, then this endpoint will try to determine if items have been moved or renamed on its own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It merely restates 'Update' and the PUT route but does not disclose whether changes are propagated, whether type changes are destructive, whether choices are validated, or what permissions are required.

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 a single clause plus a path reference, with no filler. It is front-loaded with the operation and resource, and the endpoint reference is a useful, non-redundant addition.

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?

For a tool with 11 parameters, no annotations, and no output schema, an 8-word description is insufficient. It identifies the resource correctly but leaves out high-level usage context and expected behavior, making it incomplete for reliable invocation.

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 description coverage is 91%, so the input schema already documents most parameters thoroughly, including edge cases like dropdownChoiceMap and extraBody. The tool description adds no parameter-level semantics, but the schema handles the heavy lifting.

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 names the specific operation ('Update') and the exact resource ('deals custom field'), reinforced by the PUT /dealCustomFields/{id} endpoint. This differentiates it from generic update_custom_field and from create_deal_custom_field/get_deal_custom_field.

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 intended use is implied: modify an existing deal custom field. However, it does not explicitly state when to use this tool versus alternatives like update_custom_field or create_deal_custom_field, and there are no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools