Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updateEmCampaign

DestructiveIdempotent

Update an email campaign's subject or HTML body, with merge fields allowed, to revise outreach content. Only account owners and admins can use it.

Instructions

Update an email campaign's subject or body. Only account owners and admins can do this. Merge fields are allowed.

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": {
      "id": "<id>"
    },
    "name": "updateEmCampaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCampaign ID
nameNoName
originNoOrigin
subjectNoSubject (merge fields allowed)
bodyHtmlNoHTML body (merge fields allowed)
originIdNoOrigin ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • changedInput schema / properties / bodyHtml / description
      Previous value: -"Body HTML"New value: +"HTML body (merge fields allowed)"
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Name",
      +  "type": "string"
      +}
    • changedInput schema / properties / subject / description
      Previous value: -"Subject"New value: +"Subject (merge fields allowed)"
  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?

The description adds real value beyond the annotations by disclosing the authorization requirement (account owners and admins only) and that merge fields are permitted, which the destructiveHint/idempotentHint flags do not convey. It does not explain what 'destructive' means here, whether omitted fields are preserved or cleared, or how failures are reported.

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, front-loaded sentences with no filler: what it does, who may do it, and a notable capability. Nothing is redundant with the title or restated for padding.

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 destructive, permission-gated mutation with six parameters and no output schema, the description covers identity, permissions, and merge fields but leaves update semantics (merge vs. replace behaviour for name/origin/originId) unstated. Adequate to call it, not fully sufficient to call it safely.

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 parameter documentation is already carried by the schema and a baseline of 3 applies. The description's framing that only 'subject or body' are updated is marginally at odds with the schema's additional name, origin, and originId properties, so it adds no clarifying semantics for those fields.

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?

The description gives a specific verb and resource ('Update an email campaign') and narrows scope to 'subject or body', which separates it from createEmCampaign and listEmCampaigns. It stops short of naming a sibling or explaining how it relates to updateEmEvent/updateTemplate style tools.

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: an agent can infer this is the mutation path for an existing campaign, with createEmCampaign and listEmCampaigns as the obvious neighbours. There is no explicit when-to-use or when-not-to-use statement, and no guidance on partial vs. full updates.

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