Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createDealCustomField

Creates a deal custom field in Follow Up Boss so account owners can define label, type, dropdown choices, and display settings.

Instructions

Create a deal custom field. Only the account owner can do this. label and type are required; choices applies only to dropdown fields.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "label": "<label>",
      "type": "<type>"
    },
    "name": "createDealCustomField"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesField type.
labelYesUser-friendly name of the field (e.g. Anniversary). Use label, not name.
choicesNoOptions for a dropdown field. Use choices, not options.
readOnlyNoField is read only. FUB default false.
hideIfEmptyNoHide the field when empty. FUB default false.
isRecurringNoDate field repeats every year (e.g. birthdays). FUB default false.
orderWeightNoWeight for custom sorting. FUB default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.0.0
    • changedInput schema / properties / choices / description
      Previous value: -"Dropdown choices (dropdown only)"New value: +"Options for a dropdown field. Use choices, not options."
    • addedInput schema / properties / hideIfEmpty / description
      Added value: +"Hide the field when empty. FUB default false."
    • addedInput schema / properties / isRecurring / description
      Added value: +"Date field repeats every year (e.g. birthdays). FUB default false."
    • changedInput schema / properties / label / description
      Previous value: -"User-friendly field name"New value: +"User-friendly name of the field (e.g. Anniversary). Use label, not name."
    • addedInput schema / properties / orderWeight / description
      Added value: +"Weight for custom sorting. FUB default 0."
    • changedInput schema / properties / orderWeight / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / readOnly / description
      Added value: +"Field is read only. FUB default false."
    • changedInput schema / properties / type / description
      Previous value: -"Field type: text, date, number, dropdown"New value: +"Field type."
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "text",
      +  "date",
      +  "number",
      +  "dropdown"
      +]
  2. Changed10 schema fields changedv1.1.3
    • addedInput schema / properties / choices
      Added value: +{
      +  "description": "Dropdown choices (dropdown only)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / hideIfEmpty
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / isRecurring
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / label
      Added value: +{
      +  "description": "User-friendly field name",
      +  "type": "string"
      +}
    • removedInput schema / properties / name
      Removed value: -{
      -  "description": "Field name",
      -  "type": "string"
      -}
    • removedInput schema / properties / options
      Removed value: -{
      -  "description": "Dropdown options",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • addedInput schema / properties / orderWeight
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / readOnly
      Added value: +{
      +  "type": "boolean"
      +}
    • changedInput schema / properties / type / description
      Previous value: -"Field type"New value: +"Field type: text, date, number, dropdown"
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "type"
      -]New value: +[
      +  "label",
      +  "type"
      +]
  3. First observedv1.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is covered. The description goes beyond that with the account-owner authorization requirement and the conditional rule that choices only applies to dropdown fields, both of which are non-obvious behavioural constraints. It stops short of describing what is returned (e.g. the new field's id), which matters for a create operation.

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?

Three short sentences, front-loaded with purpose, then the permission gate, then the field constraints. No filler, but the parameter clause is compressed into a single run-on line and could be structured more scannably.

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

Completeness3/5

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

For a 7-parameter mutation with no output schema, the definition covers purpose, auth, and one conditional parameter but says nothing about return values or about validating that a field with the same label does not already exist. Adequate to call it, thin on consequences of calling it.

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 coverage is 100% and the schema already marks label/type as required and documents choices as 'Options for a dropdown field', so the description's restatement of those facts adds little. The one piece of added meaning is the binding of choices to the dropdown type, which the schema only implies.

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 opens with a specific verb+resource: 'Create a deal custom field.' That is clear and separates it from updateDealCustomField and getDealCustomField. It does not explicitly distinguish itself from the sibling createCustomField (non-deal custom fields), which is the one real ambiguity in the catalogue.

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?

It states a prerequisite ('Only the account owner can do this'), which is genuinely actionable guidance for deciding whether to attempt the call. However, it gives no when-to-use vs when-to-use-alternative guidance, such as whether to prefer createCustomField or check the existing field list first.

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