Skip to main content
Glama
Sign In
Brevo MCP Server

Brevo MCP Server

by mark-o298
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

send_campaign_now

Provide a campaign ID to instantly send an email campaign.

Instructions

Send an email campaign immediately

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": {
      "campaignId": "<campaignId>"
    },
    "name": "send_campaign_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesID of the campaign to send

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.7

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided. Description only states immediacy, but no details on irreversible actions, permissions, or rate limits. For a sending action, more transparency is needed.

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?

Single sentence, front-loaded with key info. Could include more detail without being verbose, but acceptable for simple tool.

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?

Simple tool with one parameter. Minimal description is functional but lacks behavioral context (e.g., confirmation, retry behavior) that would aid agent safety.

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 clear description for campaignId. Description adds no extra meaning beyond schema, baseline score 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?

Clear action and resource: 'Send an email campaign immediately'. Distinguishes from siblings like send_email (individual) and update_campaign_status (scheduling), but does not explicitly state scope.

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 on when to use this tool versus alternatives like update_campaign_status or send_test_email. Lacks context for decision-making.

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