Skip to main content
Glama
mindwear-capitian

followupboss-mcp-server

createEvent

Create new events in Follow Up Boss CRM to track lead activities, property inquiries, and other interactions for contact management.

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates events but fails to mention critical details like required permissions, whether the operation is idempotent, error handling, or what the response contains. This is inadequate for a mutation tool with complex nested parameters.

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, efficient sentence with no wasted words. It front-loads the core purpose and includes helpful examples without unnecessary elaboration, making it easy to parse quickly.

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?

For a mutation tool with 14 parameters (including nested objects), no annotations, and no output schema, the description is insufficient. It lacks details on behavioral traits, response format, error conditions, and usage context, leaving significant gaps for an agent to operate effectively.

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 the schema fully documents all 14 parameters. The description adds no parameter-specific information beyond implying event types, which is already covered in the schema's 'type' field description. This meets the baseline for high schema coverage.

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 action ('Create a new event') and resource ('in FUB'), with examples of event types provided ('lead event, property inquiry, etc'). It distinguishes the tool's purpose from siblings like createPerson or createNote by focusing on events, though it doesn't explicitly contrast with similar tools like createEmEvent.

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 guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, typical use cases, or comparisons with sibling tools like createEmEvent or createNote, leaving the agent without usage direction.

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