Skip to main content
Glama
gray-wilbee

fub-mcp

by gray-wilbee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_person

Add a new person to Follow Up Boss CRM with contact details, tags, and custom fields. Turn on deduplicate to avoid creating duplicate records from existing matches.

Instructions

Manually add a new person. (POST /people) FUB's docs also list a wildcard "custom*" field here for reading/writing custom fields directly (e.g. a "Closing Date" field as custom.ClosingDate) — that's not a literal field name, so it's not in this tool's fixed schema. Pass custom. entries via extraBody instead. Call list_custom_fields first to get exact names. deduplicate defaults to false, meaning creating a person whose email or phone matches an existing contact creates a SEPARATE duplicate record rather than erring or merging — a common way CRMs end up full of duplicate leads. Unless the user clearly wants an intentional second/separate record (e.g. a shared household phone), pass deduplicate=true, or call get_people_check_duplicate first and confirm with the user if a likely match already exists. ⚠️ This does NOT register a new lead in FUB's sense: it creates a bare contact record only — no lead routing, no automations, no per-source workflows fire. If the user actually means "a new lead just came in" (e.g. from a website registration, an inquiry, an open house sign-in) rather than "just add this person to my CRM," use create_event instead — that's what actually triggers FUB's lead routing and automations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoA list of tags applied to the person.
priceNoThe price of the property of the person's first inquiry, or the estimated sell/buy price for this person.
stageNoThe stage the person is in. (e.g., "Lead" or "Trash". See [stage API endpoint](ref:stages-get) for more options.)Lead
emailsNoA list of email addresses associated with the person. (Specify type and value, isPrimary is not expected. The first email in the list will be the primary email address.)
phonesNoA list of phone numbers associated with the person. (Specify type and value, isPrimary is not expected. The first phone in the list will be the primary phone number.)
sourceNoThe source of the lead.
lastNameNoThe last/family name of the person.
addressesNoA list of addresses associated with the person. (These are the addresses where this person can be contacted, it is not the address of a property this person may be interested in selling or buying).
contactedNoWhether the person has been contacted or not.
createdAtNoWill set the creation time for the person, if wanting to create historical leads.
extraBodyNoExtra raw JSON body fields not explicitly listed above — e.g. custom.* fields when creating/updating people or deals. Keys and values are sent as-is.
firstNameNoThe first/given name of the person.
sourceUrlNoThis is a direct link to the information about a person at the lead provider.
assignedToNoFull name of the agent assigned to this person.
backgroundNoBackground information on the person. (Can be a multi-line string.)
extraQueryNoExtra raw query parameters not explicitly listed above — e.g. FUB custom field filters like custom.ClosingDate on /people or /deals. Keys and values are sent as-is.
deduplicateNoBy default new people will be created even if there are existing people with the same email or phone. By passing true, deduplication logic will be used and, if a person is found, a 200 response will be returned along with response data for that existing person. No changes will be made based on the payload.
timeframeIdNoID of the timeframe to move (Refer to the /timeframes endpoint for valid values of timeframeId.)
collaboratorsNoList of user ids to set as collaborators on this person. Not including a collaborator's user id in this array will remove them as a collaborator.
assignedPondIdNoID of the pond assigned to this person.
assignedUserIdNoID of the agent assigned to this person.
assignedLenderIdNoID of the lender assigned to this person.
assignedLenderNameNoFull name of the lender assigned to this person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral disclosure burden, and it does so thoroughly. It warns that deduplicate defaults to false and creates a separate duplicate record, that this tool does NOT trigger FUB lead routing or automations, and that the custom* field is not a literal field name but must be passed via extraBody. These are exactly the non-obvious behavioral traits an agent needs.

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?

Although the description is long, it is dense and every sentence earns its place: endpoint identification, custom-field workaround, duplicate risk, and lead-routing distinction. It is front-loaded with the core purpose and then layers warnings and alternatives in a logical order without tautology or 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 complex create tool with 23 parameters, no annotations, and no output schema, the description covers the most decision-critical context: duplicate behavior, custom field mechanism, and lead vs. person semantics. It does not describe response shape or return values, but that is a minor gap given the strong operational guidance provided elsewhere.

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 description coverage is 100%, so the baseline is 3, but the description adds practical param meaning beyond the schema. It explains the real-world consequence of the deduplicate default, clarifies how custom fields should be provided through extraBody, and directs the agent to list_custom_fields for exact names. This is meaningful added value over the raw 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 opens with a precise verb and resource: 'Manually add a new person. (POST /people)'. It also disambiguates this tool from create_event, explaining that creating a person is not the same as registering a lead, which makes the purpose unmistakable among many sibling tools.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance and alternatives: it says to call list_custom_fields first for custom field names, to use get_people_check_duplicate before creating when duplicates are a concern, and to use create_event instead when the user means a new lead rather than a bare CRM contact. This leaves almost no ambiguity about tool selection.

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