Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateDealCustomField

DestructiveIdempotent

Update a deal custom field by ID for account owners, sending only the fields that need to change. Use it to adjust labels, types, dropdown choices, read-only status, recurrence, or sort order.

Instructions

Update a deal custom field by ID. Only the account owner can do this. Send only fields to change.

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": {
      "id": "<id>"
    },
    "name": "updateDealCustomField"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesField ID.
typeNoField type: text, date, number or dropdown.
labelNoUser-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. Changed10 schema fields changedv2.0.0
    • addedInput schema / properties / choices / description
      Added 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."
    • changedInput schema / properties / id / description
      Previous value: -"Field ID"New value: +"Field ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • 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"New value: +"Field type: text, date, number or dropdown."
  2. Changed9 schema fields changedv1.1.3
    • addedInput schema / properties / choices
      Added value: +{
      +  "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": "Name",
      -  "type": "string"
      -}
    • removedInput schema / properties / options
      Removed value: -{
      -  "description": "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: -"Type"New value: +"Field type"
  3. First observedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare this is destructive, non-read-only, and idempotent. The description adds useful auth and partial-update context, but it does not explain what destructive effects may occur or how changing field properties affects existing data.

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 three short sentences and front-loads the core action. Every sentence contributes useful context, though the structure could be slightly sharper by separating permission and partial-update guidance.

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 an update tool with full schema coverage and annotations, the description covers the essential action, permission requirement, and partial-update behavior. It leaves out destructive consequences and response behavior, which are relevant because there is no output schema.

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 100%, so the schema already documents all parameters thoroughly. The description adds only high-level meaning through 'by ID' and 'send only fields to change,' without adding parameter-specific detail beyond the schema.

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 states a specific verb and resource: 'Update a deal custom field by ID.' This clearly distinguishes it from sibling tools such as createDealCustomField, getDealCustomField, and listDealCustomFields.

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

Usage Guidelines4/5

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

It provides a clear prerequisite: 'Only the account owner can do this,' and partial-update guidance: 'Send only fields to change.' It does not explicitly name alternatives or when-not-to-use cases, so it falls short of full routing 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