Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createEmCampaign

Create an email marketing campaign with a unique origin and originId, plus subject and HTML body that support merge fields for personalized emails.

Instructions

Create an email marketing campaign. The origin + originId pair must be unique; never reuse it. Subject and bodyHtml support merge fields.

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": {
      "origin": "<origin>",
      "originId": "<originId>"
    },
    "name": "createEmCampaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCampaign or template name
originYesName of the originating email marketing system
subjectNoEmail subject (merge fields allowed)
bodyHtmlNoHTML body (merge fields allowed)
originIdYesYour unique ID for the campaign in that system

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.0
    • changedInput schema / properties / bodyHtml / description
      Previous value: -"Email body HTML"New value: +"HTML body (merge fields allowed)"
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Campaign or template name",
      +  "type": "string"
      +}
    • changedInput schema / properties / origin / description
      Previous value: -"Campaign origin"New value: +"Name of the originating email marketing system"
    • changedInput schema / properties / originId / description
      Previous value: -"Origin ID"New value: +"Your unique ID for the campaign in that system"
    • changedInput schema / properties / subject / description
      Previous value: -"Email subject"New value: +"Email subject (merge fields allowed)"
    • changedInput schema / required
      Previous value: -[
      -  "origin",
      -  "subject",
      -  "bodyHtml"
      -]New value: +[
      +  "origin",
      +  "originId"
      +]
  2. First observedv1.1.1

TDQS

A3.9/5.0
Behavior4/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, closed-world write, so the safety profile is covered. The description adds meaningful context beyond that: duplicate origin+originId pairs will collide, and merge fields are resolved in subject/bodyHtml. It does not say what happens on a duplicate (error vs. overwrite) or whether the campaign is created in draft state, which would have pushed this to a 5.

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?

Three short sentences, zero filler, with the core action front-loaded and the hard constraint immediately after. Nothing could be removed without losing information.

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

Completeness4/5

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

For a 5-parameter create tool with full schema coverage and no output schema, the description covers action, the critical uniqueness invariant, and merge-field behavior — enough to call it correctly. It stops short of describing the failure mode on duplicate IDs or the state of the campaign after creation.

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 100%, so baseline is 3, and the description adds one genuinely new constraint not present in the schema: the origin + originId pair must be unique and must never be reused. The merge-field note for subject and bodyHtml largely duplicates the schema's own "(merge fields allowed)" text, so it earns little additional credit.

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?

Opens with a specific verb+resource: "Create an email marketing campaign." That is unambiguous and separable from createTemplate and createEmEvent, though it never explicitly contrasts itself with those siblings, so the distinction is inferred rather than stated.

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 implied by the verb (call this to create, use updateEmCampaign/listEmCampaigns otherwise), but no explicit when-to-use or when-not-to-use guidance is given, and no alternative is named. The uniqueness rule is an operational precondition rather than routing guidance.

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