Skip to main content
Glama
mindwear-capitian

followupboss-mcp-server

by mindwear-capitian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

createDealCustomField

Add new custom fields to deals in Follow Up Boss by specifying a label, type, and optional choices, enabling tailored data collection for your pipeline.

Instructions

Create a deal custom field. FUB expects 'label' (not 'name') and 'choices' (not 'options').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesField type: text, date, number, dropdown
labelYesUser-friendly field name
choicesNoDropdown choices (dropdown only)
readOnlyNo
hideIfEmptyNo
isRecurringNo
orderWeightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. First observedv1.1.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only notes the API's naming expectations for 'label' and 'choices' but does not disclose mutation side effects, required permissions, or response behavior. For a create operation, this is insufficient.

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 concise sentences, front-loaded with the primary purpose and immediately followed by the key API gotcha. No wasted words.

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 7-parameter create tool with no annotations and no output schema, the description is too sparse. It lacks information about return values, conditional requirements (e.g., choices needed when type is dropdown), and the purpose of the remaining parameters, leaving the agent under-informed for correct 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?

The description adds meaningful semantics for two key parameters by clarifying the expected API names ('label' not 'name', 'choices' not 'options'). However, with only 43% schema coverage, it does not compensate for the four undocumented boolean/number parameters (readOnly, hideIfEmpty, isRecurring, orderWeight).

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 tool creates a deal custom field, using a specific verb and resource. It distinguishes from sibling tools like createCustomField and updateDealCustomField by specifying 'deal' and 'create'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention when to use createDealCustomField over createCustomField or listDealCustomFields, nor any prerequisites or exclusions.

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