Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createPerson

Create a Follow Up Boss person record with contact details, custom fields, tags, and assignment; set source and sourceUrl at creation and enable deduplication to avoid duplicate leads.

Instructions

Create a person. Custom fields: add top-level keys prefixed 'custom' (e.g. customClosingDate; see listCustomFields). Set deduplicate=true to avoid duplicates. source and sourceUrl can only be set here, not on update.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "createPerson"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTags.
priceNoPrice point.
stageNoStage name. Default Lead on create.
emailsNoEmails. First entry becomes primary. Each needs value.
phonesNoPhones. First entry becomes primary. Each needs value.
sourceNoLead source. Can only be set at creation.
lastNameNoLast name.
addressesNoContact addresses (not property addresses).
contactedNotrue also pauses action plans.
createdAtNoCreation time, for importing historical leads.
firstNameNoFirst name.
sourceUrlNoLink to record at lead provider. Creation only.
assignedToNoAssigned agent full name.
backgroundNoBackground info; multi-line OK.
deduplicateNotrue = if email/phone matches, return that person unchanged (200). Default false.
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. Changed34 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."
    • changedInput schema / properties / collaborators / description
      Previous value: -"Collaborator user IDs"New value: +"Collaborator user IDs; omitted IDs are removed."
    • changedInput schema / properties / collaborators / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / contacted / description
      Previous value: -"Whether person has been contacted"New value: +"true also pauses action plans."
    • changedInput schema / properties / createdAt / description
      Previous value: -"ISO timestamp for creation date"New value: +"Creation time, for importing historical leads."
    • changedInput schema / properties / deduplicate / description
      Previous value: -"Check for duplicates before creating (query param)"New value: +"true = if email/phone matches, return that person unchanged (200). Default false."
    • 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 / lastName / description
      Previous value: -"Last name"New value: +"Last name."
    • changedInput schema / properties / phones / description
      Previous value: -"Phone numbers: [{value, type}]"New value: +"Phones. First entry becomes primary. Each needs value."
    • 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 / source / description
      Previous value: -"Lead source"New value: +"Lead source. Can only be set at creation."
    • changedInput schema / properties / sourceUrl / description
      Previous value: -"Source URL"New value: +"Link to record at lead provider. Creation only."
    • 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 to apply"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

A3.5/5.0
Behavior3/5

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

Annotations already flag this as a non-read-only, non-idempotent, non-destructive write. The description adds real behavioral detail beyond them: source/sourceUrl are creation-only, and deduplicate semantics imply a possible no-op return of an existing record. It does not address permissions, what is returned on success, or side effects like action plans or assignments.

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, front-loaded segments with no filler, and the creation-only constraint is placed last as a caveat where it belongs. The custom-fields clause is dense and slightly telegraphic, but every sentence carries information.

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 21-parameter, zero-required create tool with no output schema, the schema itself documents every field, and the description covers the two things it cannot: custom-field key naming and deduplication. It omits any note that a person can be created with an empty payload and says nothing about the response, but those are secondary.

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 the baseline is 3. The description does add one thing the schema cannot express: the 'custom' top-level key convention for custom fields (e.g. customClosingDate), which directly explains how to use the additionalProperties:true escape hatch. That is a genuine addition but the only one.

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?

"Create a person" gives a specific verb and resource, and the closing sentence ("source and sourceUrl can only be set here, not on update") implicitly separates it from updatePerson. It stops short of naming siblings like checkDuplicate or createPersonAttachment, so an agent still has to infer the boundary.

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?

The description offers one concrete situational cue: set deduplicate=true to avoid duplicates. That is useful, but it never says when to prefer createPerson over checkDuplicate or getPersonByEmail, nor whether creating an empty person is acceptable given zero required fields.

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