Skip to main content
Glama
mindwear-capitian

followupboss-mcp-server

createEvent

Log a lead event or property inquiry into Follow Up Boss by providing event details, person data, and optional property or campaign information.

Instructions

Create a new event in FUB (lead event, property inquiry, etc)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoSource of the event (e.g. website name)
systemNoSystem identifier
typeNoEvent type (e.g. Registration, Property Inquiry, General Inquiry)
messageNoEvent message
descriptionNoEvent description
occurredAtNoISO 8601 timestamp when event occurred
personNoPerson data: {id, firstName, lastName, stage, source, sourceUrl, contacted, price, assignedTo, assignedUserId, assignedLenderId, assignedLenderName, emails:[], phones:[], addresses:[], tags:[], custom*}
propertyNoProperty data: {street, city, state, code, mlsNumber, price, forRent, url, type, bedrooms, bathrooms, area, lot}
propertySearchNoProperty search criteria: {type, neighborhood, city, state, code, minPrice, maxPrice, minBedrooms, maxBedrooms, minBathrooms, maxBathrooms}
campaignNoCampaign tracking: {source, medium, term, content, campaign}
pageTitleNoTitle of the page where event occurred
pageUrlNoURL of the page where event occurred
pageReferrerNoReferrer URL
pageDurationNoTime spent on page in seconds
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It only mentions creation, but omits details on permissions, idempotency, side effects, or error conditions, leaving significant gaps for a mutation tool.

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 a single sentence with no redundancy, front-loading the action and resource. Every word contributes necessary information.

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?

Given the tool has 14 parameters with nested objects and no output schema, the description is too brief. It does not explain the return value, success/error handling, or provide context for complex fields, making it incomplete for a tool of this complexity.

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 description coverage is 100%, so each parameter has a description. The tool description adds no additional meaning beyond the schema, earning a baseline score of 3.

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 'Create', the resource 'event in FUB', and provides examples like 'lead event, property inquiry', making the purpose distinct among many sibling create tools.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., createAppointment, createCall). The description only implies usage through the name and examples, lacking exclusion criteria.

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