Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createEvent

Creates lead registration, inquiry, or page-view events, deduping people by phone or email and adding new contacts when needed.

Instructions

Create an event (lead registration, inquiry, page view). Dedupes the person by phone/email and creates them if new. Events older than 1 day count as historical and fire no workflows. 'Inquiry' becomes Property Inquiry if property is set, else General Inquiry.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "createEvent"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoEvent type.
personNo
sourceNoLead source name.
systemNoName of the system providing the lead.
messageNoMessage from the lead about the inquiry.
pageUrlNoPage URL (Viewed Page).
campaignNo
propertyNo
pageTitleNoPage title (Viewed Page).
occurredAtNoWhen it occurred (ISO 8601). Docs type it as date.
descriptionNoAdditional info about the inquiry.
pageDurationNoSeconds on page.
pageReferrerNoReferrer URL; also set pageUrl.
propertySearchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed25 schema fields changedv2.0.0
    • removedInput schema / properties / campaign / description
      Removed value: -"Campaign tracking: {source, medium, term, content, campaign}"
    • addedInput schema / properties / campaign / properties
      Added value: +{
      +  "campaign": {
      +    "description": "Campaign name",
      +    "type": "string"
      +  },
      +  "content": {
      +    "description": "Content",
      +    "type": "string"
      +  },
      +  "medium": {
      +    "description": "e.g. organic",
      +    "type": "string"
      +  },
      +  "source": {
      +    "description": "Campaign source, e.g. Google",
      +    "type": "string"
      +  },
      +  "term": {
      +    "description": "Search terms",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / campaign / required
      Added value: +[
      +  "source"
      +]
    • changedInput schema / properties / description / description
      Previous value: -"Event description"New value: +"Additional info about the inquiry."
    • changedInput schema / properties / message / description
      Previous value: -"Event message"New value: +"Message from the lead about the inquiry."
    • changedInput schema / properties / occurredAt / description
      Previous value: -"ISO 8601 timestamp when event occurred"New value: +"When it occurred (ISO 8601). Docs type it as date."
    • changedInput schema / properties / pageDuration / description
      Previous value: -"Time spent on page in seconds"New value: +"Seconds on page."
    • changedInput schema / properties / pageDuration / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / pageReferrer / description
      Previous value: -"Referrer URL"New value: +"Referrer URL; also set pageUrl."
    • changedInput schema / properties / pageTitle / description
      Previous value: -"Title of the page where event occurred"New value: +"Page title (Viewed Page)."
    • changedInput schema / properties / pageUrl / description
      Previous value: -"URL of the page where event occurred"New value: +"Page URL (Viewed Page)."
    • addedInput schema / properties / person / additionalProperties
      Added value: +true
    • removedInput schema / properties / person / description
      Removed value: -"Person data: {id, firstName, lastName, stage, source, sourceUrl, contacted, price, assignedTo, assignedUserId, assignedLenderId, assignedLenderName, emails:[], phones:[], addresses:[], tags:[], custom*}"
    • addedInput schema / properties / person / properties
      Added value: +{
      +  "addresses": {
      +    "description": "Contact addresses (not property addresses).",
      +    "items": {
      +      "properties": {
      +        "city": {
      +          "description": "City",
      +          "type": "string"
      +        },
      +        "code": {
      +          "description": "ZIP code as string",
      +          "type": "string"
      +        },
      +        "country": {
      +          "description": "Country name",
      +          "type": "string"
      +        },
      +        "state": {
      +          "description": "2-letter state code",
      +          "type": "string"
      +        },
      +        "street": {
      +          "description": "Street",
      +          "type": "string"
      +        },
      +        "type": {
      +          "description": "home (default), work, mailing, investment",
      +          "type": "string"
      +        }
      +      },
      +      "required": [],
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "assignedLenderId": {
      +    "description": "Lender user ID",
      +    "type": "integer"
      +  },
      +  "assignedLenderName": {
      +    "description": "Lender full name",
      +    "type": "string"
      +  },
      +  "assignedTo": {
      +    "description": "Agent full name",
      +    "type": "string"
      +  },
      +  "assignedUserId": {
      +    "description": "Agent user ID",
      +    "type": "integer"
      +  },
      +  "contacted": {
      +    "description": "Default false",
      +    "type": "boolean"
      +  },
      +  "emails": {
      +    "description": "Emails. First entry becomes primary. Each needs value.",
      +    "items": {
      +      "properties": {
      +        "isPrimary": {
      +          "description": "Not needed; first entry is primary",
      +          "type": "boolean"
      +        },
      +        "type": {
      +          "description": "e.g. work, home",
      +          "type": "string"
      +        },
      +        "value": {
      +          "description": "Email address",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "value"
      +      ],
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "firstName": {
      +    "description": "First name",
      +    "type": "string"
      +  },
      +  "id": {
      +    "description": "Existing person ID; 404 if not found.",
      +    "type": "integer"
      +  },
      +  "lastName": {
      +    "description": "Last name",
      +    "type": "string"
      +  },
      +  "phones": {
      +    "description": "Phones. First entry becomes primary. Each needs value.",
      +    "items": {
      +      "properties": {
      +        "isPrimary": {
      +          "description": "Not needed; first entry is primary",
      +          "type": "boolean"
      +        },
      +        "type": {
      +          "description": "e.g. mobile, home, fax",
      +          "type": "string"
      +        },
      +        "value": {
      +          "description": "Phone number, e.g. 888-555-1234",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "value"
      +      ],
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "price": {
      +    "description": "Estimated price",
      +    "type": "integer"
      +  },
      +  "source": {
      +    "description": "Lead source",
      +    "type": "string"
      +  },
      +  "sourceUrl": {
      +    "description": "Link to record at lead provider",
      +    "type": "string"
      +  },
      +  "stage": {
      +    "description": "Stage name, e.g. Lead",
      +    "type": "string"
      +  },
      +  "tags": {
      +    "description": "Tags to apply",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +}
    • addedInput schema / properties / person / required
      Added value: +[]
    • removedInput schema / properties / property / description
      Removed value: -"Property data: {street, city, state, code, mlsNumber, price, forRent, url, type, bedrooms, bathrooms, area, lot}"
    • addedInput schema / properties / property / properties
      Added value: +{
      +  "area": {
      +    "description": "Square feet",
      +    "type": "string"
      +  },
      +  "bathrooms": {
      +    "description": "Bathrooms",
      +    "type": "string"
      +  },
      +  "bedrooms": {
      +    "description": "Bedrooms",
      +    "type": "string"
      +  },
      +  "city": {
      +    "description": "City",
      +    "type": "string"
      +  },
      +  "code": {
      +    "description": "ZIP",
      +    "type": "string"
      +  },
      +  "forRent": {
      +    "description": "true if for rent",
      +    "type": "boolean"
      +  },
      +  "lot": {
      +    "description": "Acres",
      +    "type": "string"
      +  },
      +  "mlsNumber": {
      +    "description": "MLS number",
      +    "type": "string"
      +  },
      +  "price": {
      +    "description": "Asking price",
      +    "type": "integer"
      +  },
      +  "state": {
      +    "description": "State code",
      +    "type": "string"
      +  },
      +  "street": {
      +    "description": "Street",
      +    "type": "string"
      +  },
      +  "type": {
      +    "description": "Freeform type, e.g. Bungalow",
      +    "type": "string"
      +  },
      +  "url": {
      +    "description": "Listing URL",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / property / required
      Added value: +[]
    • removedInput schema / properties / propertySearch / description
      Removed value: -"Property search criteria: {type, neighborhood, city, state, code, minPrice, maxPrice, minBedrooms, maxBedrooms, minBathrooms, maxBathrooms}"
    • addedInput schema / properties / propertySearch / properties
      Added value: +{
      +  "city": {
      +    "description": "City",
      +    "type": "string"
      +  },
      +  "code": {
      +    "description": "ZIP codes",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "maxBathrooms": {
      +    "description": "Max baths",
      +    "type": "number"
      +  },
      +  "maxBedrooms": {
      +    "description": "Max beds",
      +    "type": "integer"
      +  },
      +  "maxPrice": {
      +    "description": "Max price",
      +    "type": "integer"
      +  },
      +  "minBathrooms": {
      +    "description": "Min baths",
      +    "type": "number"
      +  },
      +  "minBedrooms": {
      +    "description": "Min beds",
      +    "type": "integer"
      +  },
      +  "minPrice": {
      +    "description": "Min price",
      +    "type": "integer"
      +  },
      +  "neighborhood": {
      +    "description": "Neighborhood",
      +    "type": "string"
      +  },
      +  "state": {
      +    "description": "State",
      +    "type": "string"
      +  },
      +  "type": {
      +    "description": "e.g. Residential, Lot",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / propertySearch / required
      Added value: +[]
    • changedInput schema / properties / source / description
      Previous value: -"Source of the event (e.g. website name)"New value: +"Lead source name."
    • changedInput schema / properties / system / description
      Previous value: -"System identifier"New value: +"Name of the system providing the lead."
    • changedInput schema / properties / type / description
      Previous value: -"Event type (e.g. Registration, Property Inquiry, General Inquiry)"New value: +"Event type."
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "Registration",
      +  "Inquiry",
      +  "Seller Inquiry",
      +  "Property Inquiry",
      +  "General Inquiry",
      +  "Viewed Property",
      +  "Saved Property",
      +  "Visited Website",
      +  "Incoming Call",
      +  "Unsubscribed",
      +  "Property Search",
      +  "Saved Property Search",
      +  "Visited Open House",
      +  "Viewed Page"
      +]
  2. First observedv1.1.1

TDQS

A4.1/5.0
Behavior5/5

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

With annotations already declaring non-readOnly, non-idempotent, non-destructive, and closed-world, the description still adds substantial unseen behavior: person deduplication by phone/email, implicit person creation when new, suppression of workflows for events older than one day, and silent type coercion of "Inquiry" into Property Inquiry or General Inquiry. These are exactly the consequences an agent cannot infer from structured fields.

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

Conciseness4/5

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

Four tight sentences, front-loaded with the action and event kinds, then escalating to dedupe behavior, the historical cutoff, and the type rule. No filler; only a slightly denser wrap-up sentence about 'Inquiry' costs it a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter tool with deep nested objects and no output schema, the description covers the highest-risk unknowns: side effects on the person record, workflow firing suppression, and type coercion. Return values are left unspecified, but the behavioral contract an agent needs to call this safely is present.

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 coverage is 71%, so the schema carries most field-level meaning and a baseline of 3 would apply. The description earns extra credit by explaining cross-field semantics the schema does not: how the 'type' value mutates based on whether a property object is supplied, and that person identity is resolved from phones/emails rather than requiring an id.

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?

States a specific verb and resource ("Create an event") and immediately grounds it with concrete event kinds (lead registration, inquiry, page view), so an agent knows the domain. It does not, however, differentiate itself from lookalike siblings such as createEmEvent, createCall, or createNote, so the agent must infer boundaries from the type enum.

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?

Usage is only implied: the parenthetical event list and the "Inquiry" branching rule suggest when the tool applies, but there is no explicit when-to-use vs. when-to-use-something-else guidance. The "older than 1 day counts as historical" note is a behavioral constraint rather than routing advice.

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