Skip to main content
Glama
mindwear-capitian

followupboss-mcp-server

createPerson

Add a new person to Follow Up Boss with contact details, tags, pipeline stage, and assignment options.

Instructions

Create a new person/contact in FUB

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags to apply
priceNoPrice point
stageNoPipeline stage
emailsNoEmail addresses: [{value, type}]
phonesNoPhone numbers: [{value, type}]
sourceNoLead source
lastNameNoLast name
addressesNoAddresses: [{street, city, state, code, type}]
contactedNoWhether person has been contacted
createdAtNoISO timestamp for creation date
firstNameNoFirst name
sourceUrlNoSource URL
assignedToNoAssigned agent name
backgroundNoBackground info
deduplicateNoCheck for duplicates before creating (query param)
timeframeIdNoTimeframe ID
collaboratorsNoCollaborator user IDs
assignedPondIdNoAssigned pond ID
assignedUserIdNoAssigned user ID
assignedLenderIdNoAssigned lender ID
assignedLenderNameNoAssigned lender name
Behavior2/5

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

With no annotations, the description provides no behavioral details. It does not discuss side effects (e.g., webhooks, related record creation), error handling, or the effect of the deduplicate parameter. This is a significant gap for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single very short sentence. While front-loaded, it lacks structure and depth, providing minimal information that does not earn its place given the complexity of the tool.

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?

Despite 21 all-optional parameters and no output schema, the description does not explain what the tool returns, required combinations (e.g., at least one of firstName/lastName/emails), or success/failure indicators. Incomplete for practical use.

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 schema already documents each parameter. The description adds no extra meaning or context about how parameters relate or should be used together, achieving only baseline adequacy.

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 clearly states the verb 'Create', resource 'person/contact', and platform 'FUB', distinguishing it from sibling tools like updatePerson or createDeal. However, it could be more specific about the domain context.

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 usage guidance is provided. The description does not mention when to use this tool, alternatives (e.g., checkDuplicate), prerequisites, or best practices for handling duplicates or required fields.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mindwear-capitian/followupboss-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server