Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listEmCampaigns

Read-onlyIdempotent

Retrieve email marketing campaigns from Follow Up Boss, with optional filters for origin system and origin ID to find specific campaigns or review campaign lists.

Instructions

List email marketing campaigns, optionally by origin system and origin ID.

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

Input Schema

NameRequiredDescriptionDefault
limitNoResults to return. FUB default 10, max 100.
offsetNoRows to skip before results begin. Default 0.
originNoOnly campaigns from this origin system
originIdNoOnly the campaign with this ID in the origin system

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / origin
      Added value: +{
      +  "description": "Only campaigns from this origin system",
      +  "type": "string"
      +}
    • addedInput schema / properties / originId
      Added value: +{
      +  "description": "Only the campaign with this ID in the origin system",
      +  "type": "string"
      +}
  2. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that filtering is optional; it says nothing about default page size, ordering, or what a campaign record contains, which the agent cannot infer elsewhere.

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?

A single front-loaded sentence with zero filler; the resource comes first and the optional filter scope follows immediately.

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?

For a four-parameter read-only list tool with full schema coverage and complete annotations, the description is minimally sufficient. However, with no output schema present, the absence of any note on return shape or result ordering leaves an agent without information it cannot get elsewhere.

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 coverage is 100%, with each of limit, offset, origin and originId documented in the schema itself, so baseline is 3. The description adds the useful nuance that the origin filters are optional but does not clarify whether originId can be used without origin.

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 ('List email marketing campaigns') and names the two filter axes. It is clearly separable from siblings like listEmEvents and listTextMessageTemplates, though it never explicitly contrasts itself with them.

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?

'Optionally by origin system and origin ID' implies when the filters apply, but there is no explicit guidance on when to use this versus a single-campaign lookup or sibling event listing, and no mention of pagination expectations when using limit/offset.

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