Skip to main content
Glama
mindwear-capitian

followupboss-mcp-server

updateEmCampaign

Update an existing email marketing campaign by specifying its ID and optionally changing subject, body, origin, or origin ID.

Instructions

Update an email marketing campaign

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCampaign ID
originNoOrigin
originIdNoOrigin ID
subjectNoSubject
bodyHtmlNoBody HTML
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only states 'Update' without explaining side effects, authorization needs, or whether partial updates are supported. Important details about what happens to unspecified fields or the campaign's state are omitted.

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?

The description is extremely concise with a single sentence containing no filler. However, it is slightly under-specified; a bit more context would improve clarity without sacrificing brevity.

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

Completeness2/5

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

Given the tool has 5 parameters and no output schema, the description is insufficient. It fails to explain the return value, side effects, or how to interpret results, leaving an AI agent underinformed for correct invocation.

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?

The input schema has 100% description coverage, so the baseline is 3. The tool description adds no additional meaning beyond the schema descriptions; it does not clarify parameter usage, constraints, or relationships.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Update') and the resource ('an email marketing campaign'), which distinguishes it from sibling tools like createEmCampaign and listEmCampaigns. It is specific and unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives such as createEmCampaign or deleteEmCampaign. The context of updating versus creating is implied but not explicitly stated, and no exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mindwear-capitian/followupboss-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server