Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createEmEvent

Sends up to 1,000 email marketing events per call to Follow Up Boss, tracking opens, clicks, bounces, and unsubscribes; recipients without matching contacts are skipped and listed.

Instructions

Send email marketing events to FUB, up to 1000 per call. Recipients with no matching contact are skipped and listed in recipientsNotFound.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "emEvents": "<emEvents>"
    },
    "name": "createEmEvent"
  }
}

Input Schema

NameRequiredDescriptionDefault
emEventsYesEvent objects (max 1000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • removedInput schema / properties / campaignId
      Removed value: -{
      -  "description": "Campaign ID",
      -  "type": "number"
      -}
    • addedInput schema / properties / emEvents
      Added value: +{
      +  "description": "Event objects (max 1000)",
      +  "items": {
      +    "properties": {
      +      "campaignId": {
      +        "description": "Campaign id returned by createEmCampaign",
      +        "type": "string"
      +      },
      +      "occurred": {
      +        "description": "Date-time of the event, ISO 8601",
      +        "type": "string"
      +      },
      +      "personId": {
      +        "description": "FUB person ID of the recipient",
      +        "type": "number"
      +      },
      +      "recipient": {
      +        "description": "Recipient email address",
      +        "type": "string"
      +      },
      +      "type": {
      +        "description": "Event type",
      +        "enum": [
      +          "delivered",
      +          "open",
      +          "click",
      +          "bounced",
      +          "soft-bounce",
      +          "hard-bounce",
      +          "unsubscribe",
      +          "spamreport",
      +          "dropped"
      +        ],
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "URL for the campaign",
      +        "type": "string"
      +      },
      +      "userId": {
      +        "description": "Sending user ID; defaults to the API key's user",
      +        "type": "number"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / properties / events
      Removed value: -{
      -  "description": "Events array: [{type, email, timestamp}]",
      -  "items": {
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "campaignId",
      -  "events"
      -]New value: +[
      +  "emEvents"
      +]
  2. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, non-idempotent, non-destructive write. The description does add real value beyond them: the 1000-per-call ceiling and the fact that unmatched recipients are silently skipped and reported back in recipientsNotFound, which tells the agent partial success is possible. It stops short of covering retry/duplicate semantics for a non-idempotent batch write.

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?

Two sentences, front-loaded with the action and batch limit, then the failure mode. No filler, though the 'up to 1000 per call' clause duplicates the schema and could be trimmed.

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

Completeness3/5

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

There is no output schema, and the description only characterizes one response field (recipientsNotFound) without describing the shape of success results or error handling for a batch write. For a single-parameter batch ingestion tool this is adequate but not complete.

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% and every nested event field (type enum, recipient, personId, campaignId, occurred) is documented in the schema. The description's only parameter note, the 1000 cap, repeats the schema's own 'max 1000' text, so it adds essentially nothing beyond structured data.

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: 'Send email marketing events to FUB' with batch scope. This is clearly distinguishable from listEmEvents and createEmCampaign in the sibling set, though it never names those siblings explicitly the way a 5 would.

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 context is only implied: the note that recipients without a matching contact are skipped hints that contacts must already exist before sending events, but there is no explicit when-to-use, prerequisites, or routing versus listEmEvents/createEmCampaign.

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