Skip to main content
Glama
mark-o298

Brevo MCP Server

by mark-o298

create_email_campaign

Create new email campaigns with customizable subject, sender, HTML content, and targeting options like lists or segments. Supports scheduling and A/B testing.

Instructions

Create a new email campaign in Brevo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesInternal campaign name
subjectYesEmail subject line
senderNoSender information (optional - defaults to verified sender from account)
htmlContentNoHTML content of the email
htmlUrlNoURL to fetch HTML content from
templateIdNoID of existing Brevo template to use
listIdsNoList IDs to send campaign to
exclusionListIdsNoList IDs to exclude from campaign
segmentIdsNoSegment IDs to target
typeNoCampaign typeclassic
tagNoCampaign tag for organization
replyToNoReply-to email address
scheduledAtNoISO 8601 datetime to schedule campaign
abTestingNoEnable A/B testing
sendAtBestTimeNoEnable send time optimization
utmCampaignNoUTM campaign parameter for tracking
paramsNoTemplate parameters if using templateId
Behavior2/5

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

The description lacks behavioral details such as required permissions, rate limits, or side effects. With no annotations, the description carries full burden but reveals nothing beyond the basic create operation.

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 a single concise sentence with no fluff. However, for a complex tool with many parameters, a slightly more structured breakdown could be beneficial.

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 complexity (17 parameters, nested objects, no output schema, no annotations), the description is insufficient. It does not explain return values, parameter dependencies, or default behaviors.

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?

All 17 parameters have descriptions in the schema (100% coverage), so the description adds no extra meaning beyond what is already in the schema. Baseline score of 3 is appropriate.

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 clearly states the action (create) and resource (email campaign) within Brevo. It is unambiguous but does not differentiate from sibling tools like 'update_email_campaign' or 'send_campaign_now'.

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, nor any prerequisites or exclusions. The user must infer usage from context.

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/mark-o298/brevo-mcp'

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