Skip to main content
Glama
mindwear-capitian

followupboss-mcp-server

listPeople

Search and filter people in Follow Up Boss by name, email, phone, tags, stage, source, assigned agent, price range, smart list, and more.

Instructions

List/search people in FUB. Supports filtering by name, email, phone, tags, stage, source, assignedTo, price range, smart list, and more. For tag filtering use the tags parameter (comma-separated, OR logic). For email lookup use the email parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoComma-separated person IDs
sortNoSort order
limitNoMaximum number of results to return
offsetNoOffset for pagination
nextNoCursor for next page of results
fieldsNoComma-separated list of fields to return
lastActivityAfterNoISO date - only people with activity after this date
lastActivityBeforeNoISO date - only people with activity before this date
nameNoSearch by name
firstNameNoFilter by first name
lastNameNoFilter by last name
emailNoFilter by email
phoneNoFilter by phone
stageNoFilter by stage
sourceNoFilter by source
assignedToNoFilter by assigned agent name
assignedUserIdNoFilter by assigned user ID
assignedPondIdNoFilter by assigned pond ID
assignedLenderNameNoFilter by lender name
assignedLenderIdNoFilter by lender ID
contactedNoFilter by contacted status
priceAboveNoMinimum price filter
priceBelowNoMaximum price filter
smartListIdNoFilter by smart list ID
includeTrashNoInclude trashed people
includeUnclaimedNoInclude unclaimed people
tagsNoComma-separated tags to filter by
Behavior3/5

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

No annotations are present, so the description carries the burden. It does not disclose behavioral traits such as read-only status, rate limits, pagination behavior, or sorting defaults. The parameter schema hints at pagination but the description omits it.

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?

Three sentences with no wasted words. The first sentence states the purpose, the second lists filters, and the third gives specific usage guidance. Well front-loaded.

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?

With 27 parameters and no output schema, the description covers essential filters but does not explain return structure or pagination limits. It mentions 'max results' implicitly via schema but lacks default values.

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% (baseline 3). The description adds value by explaining tag usage (comma-separated, OR logic) and email lookup, going beyond the schema descriptions.

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 clearly states the verb 'list/search' and the resource 'people in FUB', and distinguishes it from sibling tools like getPerson (single person) and createPerson (creation).

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?

Provides guidance for specific filter usage (tags with comma-separated OR logic, email lookup). However, does not explicitly state when not to use this tool or mention alternatives like listUnclaimed.

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