Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listEmEvents

Read-onlyIdempotent

Retrieve email marketing events such as delivered, opened, clicked, bounced, or unsubscribed, with filters by event type, person ID, and update date to track campaign engagement.

Instructions

List email marketing events (delivered, opened, clicked, etc).

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": "listEmEvents"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by event type
limitNoResults to return. FUB default 10, max 100.
offsetNoRows to skip before results begin. Default 0.
personIdNoFilter by person ID
updatedAfterNoISO date-time; events created or updated after this

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"Results to return. FUB default 10, max 100."
    • changedInput schema / properties / offset / description
      Previous value: -"Offset for pagination"New value: +"Rows to skip before results begin. Default 0."
    • addedInput schema / properties / personId
      Added value: +{
      +  "description": "Filter by person ID",
      +  "type": "number"
      +}
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Filter by event type",
      +  "enum": [
      +    "delivered",
      +    "open",
      +    "click",
      +    "bounced",
      +    "soft-bounce",
      +    "hard-bounce",
      +    "unsubscribe",
      +    "spamreport",
      +    "dropped"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / updatedAfter
      Added value: +{
      +  "description": "ISO date-time; events created or updated after this",
      +  "type": "string"
      +}
  2. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and side-effect profile is fully covered. The description adds nothing beyond that — no ordering, no whether results span all campaigns/people, no note that filtering is optional and unfiltered calls may return large volumes.

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?

A single front-loaded sentence with zero filler — appropriately sized for a simple read tool. It is arguably too terse for the tool's five filter parameters, but nothing in it is wasted.

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, so the description is the only place to say what a returned event looks like (fields, ordering, whether payloads/timestamps are included), and it does not. With annotations carrying the behavior profile and the schema carrying the parameters, the definition is minimally workable but leaves the return shape opaque.

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 every parameter (type enum, limit with FUB default 10/max 100, offset, personId, updatedAfter) is already documented in the schema. The description only echoes the event-type concept, adding no syntax or semantics on top, so the baseline 3 applies.

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 (List) and a specific resource (email marketing events) and gives examples of event kinds, which implicitly separates it from the generic sibling listEvents. However, it never names listEvents or createEmEvent, so the agent must infer the distinction from the 'email marketing' qualifier alone.

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?

There is no when-to-use guidance, no statement about when to prefer this over listEvents or the em-campaign tools, and no prerequisites or exclusions. The agent is left to infer applicability purely from the noun phrase.

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