Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createCustomField

Creates a custom field in Follow Up Boss for account owners, defining label and field type such as text, date, number, or dropdown. Use it to add new data points to contacts before the type is locked in.

Instructions

Create a custom field (account owners only). The type cannot be changed later.

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": "createCustomField"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesField type; fixed after creation
labelYesUser-facing field name, e.g. Anniversary
choicesNoOptions for a dropdown field
hideIfEmptyNoHide on the person view when empty. Default false
isRecurringNoDate fields only: recurs yearly (birthdays). Default false
orderWeightNoSort weight. Default 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.0.0
    • addedInput schema / properties / choices
      Added value: +{
      +  "description": "Options for a dropdown field",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / hideIfEmpty
      Added value: +{
      +  "description": "Hide on the person view when empty. Default false",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / isRecurring
      Added value: +{
      +  "description": "Date fields only: recurs yearly (birthdays). Default false",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / label
      Added value: +{
      +  "description": "User-facing field name, e.g. Anniversary",
      +  "type": "string"
      +}
    • removedInput schema / properties / name
      Removed value: -{
      -  "description": "Field name",
      -  "type": "string"
      -}
    • removedInput schema / properties / options
      Removed value: -{
      -  "description": "Options for dropdown fields",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • addedInput schema / properties / orderWeight
      Added value: +{
      +  "description": "Sort weight. Default 0",
      +  "type": "number"
      +}
    • changedInput schema / properties / type / description
      Previous value: -"Field type (text, number, dropdown, etc)"New value: +"Field type; fixed after creation"
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "text",
      +  "date",
      +  "number",
      +  "dropdown"
      +]
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "type"
      -]New value: +[
      +  "label",
      +  "type"
      +]
  2. First observedv1.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (non-readonly, non-destructive, non-idempotent, closed-world). The description adds two non-obvious facts beyond them: the account-owner authorization gate and the permanent immutability of the field type, both of which affect how an agent should call and re-call the tool.

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 short sentences, front-loaded with the action and immediately followed by the two constraints that matter most. Nothing is redundant or padded.

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 six-parameter creation tool with no output schema, the description leaves the target entity type ambiguous against createDealCustomField and says nothing about the cost of a wrong call given the irreversible type choice. Schema and annotations carry most of the weight, but the missing disambiguation is a real gap.

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%, so every parameter including the type enum, choices, hideIfEmpty, isRecurring, and orderWeight is already documented in the schema. The description only reinforces the type-immutability note and adds no cross-parameter guidance, such as that choices matters only for the dropdown type.

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 states a specific verb and resource ("Create a custom field"), which distinguishes it from getCustomField/updateCustomField/listCustomFields. However, it does not say which object the field attaches to, so it does not clearly separate itself from the sibling createDealCustomField.

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?

Usage is only implied by the verb "Create"; there is no statement of when to prefer this over createDealCustomField or of any prerequisite such as first inspecting listCustomFields. The "account owners only" parenthetical is a permission constraint rather than when-to-use guidance.

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