Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updatePerson

DestructiveIdempotent

Update a Follow Up Boss person record by ID, changing tags, phones, emails, stage, assignment, addresses, and custom fields while controlling tag merging and phone replacement.

Instructions

Update a person. tags replaces all tags unless mergeTags=true; phones replaces all numbers. Custom fields: top-level 'custom*' keys; JSON null clears one. source/sourceUrl cannot be changed.

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

Input Schema

NameRequiredDescriptionDefault
idYesPerson ID to update.
tagsNoTags.
priceNoPrice point.
stageNoStage name. Default Lead on create.
emailsNoEmails. First entry becomes primary. Each needs value.
phonesNoPhones. REPLACES all existing numbers (incl. relationship ones); resend ones to keep.
lastNameNoLast name.
addressesNoContact addresses (not property addresses).
contactedNotrue also pauses action plans.
firstNameNoFirst name.
mergeTagsNotrue = add tags to existing; otherwise tags REPLACES all tags.
assignedToNoAssigned agent full name.
backgroundNoBackground info; multi-line OK.
timeframeIdNoTimeframe ID (see listTimeframes).
collaboratorsNoCollaborator user IDs; omitted IDs are removed.
assignedPondIdNoAssigned pond ID.
assignedUserIdNoAssigned user ID.
assignedLenderIdNoLender user ID.
assignedLenderNameNoLender full name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed32 schema fields changedv2.0.0
    • addedInput schema / additionalProperties
      Added value: +true
    • changedInput schema / properties / addresses / description
      Previous value: -"Addresses: [{street, city, state, code, type}]"New value: +"Contact addresses (not property addresses)."
    • addedInput schema / properties / addresses / items / properties
      Added value: +{
      +  "city": {
      +    "description": "City",
      +    "type": "string"
      +  },
      +  "code": {
      +    "description": "ZIP code as string",
      +    "type": "string"
      +  },
      +  "country": {
      +    "description": "Country name",
      +    "type": "string"
      +  },
      +  "state": {
      +    "description": "2-letter state code",
      +    "type": "string"
      +  },
      +  "street": {
      +    "description": "Street",
      +    "type": "string"
      +  },
      +  "type": {
      +    "description": "home (default), work, mailing, investment",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / addresses / items / required
      Added value: +[]
    • changedInput schema / properties / assignedLenderId / description
      Previous value: -"Assigned lender ID"New value: +"Lender user ID."
    • changedInput schema / properties / assignedLenderId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / assignedLenderName / description
      Previous value: -"Assigned lender name"New value: +"Lender full name."
    • changedInput schema / properties / assignedPondId / description
      Previous value: -"Assigned pond ID"New value: +"Assigned pond ID."
    • changedInput schema / properties / assignedPondId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / assignedTo / description
      Previous value: -"Assigned agent name"New value: +"Assigned agent full name."
    • changedInput schema / properties / assignedUserId / description
      Previous value: -"Assigned user ID"New value: +"Assigned user ID."
    • changedInput schema / properties / assignedUserId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / background / description
      Previous value: -"Background info"New value: +"Background info; multi-line OK."
    • addedInput schema / properties / collaborators
      Added value: +{
      +  "description": "Collaborator user IDs; omitted IDs are removed.",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / contacted / description
      Previous value: -"Contacted status"New value: +"true also pauses action plans."
    • changedInput schema / properties / emails / description
      Previous value: -"Email addresses: [{value, type}]"New value: +"Emails. First entry becomes primary. Each needs value."
    • addedInput schema / properties / emails / items / properties
      Added value: +{
      +  "isPrimary": {
      +    "description": "Not needed; first entry is primary",
      +    "type": "boolean"
      +  },
      +  "type": {
      +    "description": "e.g. work, home",
      +    "type": "string"
      +  },
      +  "value": {
      +    "description": "Email address",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / emails / items / required
      Added value: +[
      +  "value"
      +]
    • changedInput schema / properties / firstName / description
      Previous value: -"First name"New value: +"First name."
    • changedInput schema / properties / id / description
      Previous value: -"Person ID to update"New value: +"Person ID to update."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / lastName / description
      Previous value: -"Last name"New value: +"Last name."
    • changedInput schema / properties / mergeTags / description
      Previous value: -"Merge tags instead of replacing (query param)"New value: +"true = add tags to existing; otherwise tags REPLACES all tags."
    • changedInput schema / properties / phones / description
      Previous value: -"Phone numbers: [{value, type}]"New value: +"Phones. REPLACES all existing numbers (incl. relationship ones); resend ones to keep."
    • addedInput schema / properties / phones / items / properties
      Added value: +{
      +  "isPrimary": {
      +    "description": "Not needed; first entry is primary",
      +    "type": "boolean"
      +  },
      +  "type": {
      +    "description": "e.g. mobile, home, fax",
      +    "type": "string"
      +  },
      +  "value": {
      +    "description": "Phone number, e.g. 888-555-1234",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / phones / items / required
      Added value: +[
      +  "value"
      +]
    • changedInput schema / properties / price / description
      Previous value: -"Price point"New value: +"Price point."
    • changedInput schema / properties / price / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / stage / description
      Previous value: -"Pipeline stage"New value: +"Stage name. Default Lead on create."
    • changedInput schema / properties / tags / description
      Previous value: -"Tags"New value: +"Tags."
    • changedInput schema / properties / timeframeId / description
      Previous value: -"Timeframe ID"New value: +"Timeframe ID (see listTimeframes)."
    • changedInput schema / properties / timeframeId / type
      Previous value: -"number"New value: +"integer"
  2. First observedv1.1.1

TDQS

A4.1/5.0
Behavior5/5

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

The annotations already mark this as destructive and idempotent, and the description adds concrete destructive semantics: tags replace unless mergeTags=true, phones replace all numbers, and JSON null clears custom fields. It also identifies source/sourceUrl as immutable, which is valuable behavioral context beyond the annotations.

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 four compact clauses, front-loading the action and then immediately listing the destructive or immutable edge cases. Every clause carries useful information with no filler.

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

Completeness4/5

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

For a 19-parameter mutation tool with full schema coverage and destructive/idempotent annotations, the description covers the main behavioral traps. It could be slightly more complete by stating whether omitted fields are left unchanged, but the critical replacement and immutability semantics are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for tags, mergeTags, phones, custom* keys, and source/sourceUrl. It does not explain every one of the 19 parameters, but it highlights the most dangerous and non-obvious ones.

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, 'Update a person,' so the core action is unambiguous. It does not distinguish this tool from nearby siblings such as bulkUpdatePeople or updatePersonAttachment, though the field-level notes help scope it.

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 explains the important choice between replacing and merging tags via mergeTags, and warns that phones replace all numbers. It does not explicitly say when to use updatePerson versus bulkUpdatePeople or updatePersonAttachment, leaving sibling routing implied.

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