Skip to main content
Glama
ATOM00blue

Drin MCP Server

by ATOM00blue

create_campaign

Create a campaign draft that targets a segment or all subscribed contacts, optionally gated by a topic. Content can be a saved template or inline HTML with merge variables. Requires approval before sending.

Instructions

Create a campaign DRAFT (nothing sends yet — send_campaign starts the flow). Audience = segmentId (omit for all subscribed contacts), optionally gated by topicId (only contacts opted into that topic). Content = a saved templateId OR inline subject+html/text — never both. approvalRequired defaults to true: the send will park for human approval by email reply. Drafting is free on every plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlNoInline HTML body (supports {{merge}} vars incl. unsubscribe_url/preferences_url).
nameYesInternal campaign name.
textNoInline plain-text body.
senderNoProduct/sender externalId sent as X-Drin-Sender. Required only for account-wide API keys; overrides the server's default sender.
replyToNoReply-To address.
subjectNoInline subject (required with inline html/text; supports {{merge}} vars).
topicIdNoPreference topic gate — only contacts effectively opted in receive it.
fromNameNoDisplay name for the From header.
fromEmailYesSender address — must be on a domain verified for this product.
segmentIdNoSaved segment to target. Omit for all subscribed contacts.
templateIdNoSaved template id to render per recipient (XOR inline content).
scheduledAtNoISO-8601 time to start dispatch (after approval). Omit for ASAP.
throttlePerHourNoMax recipients per hour. Omit for full speed.
approvalRequiredNoDefault true — the send parks in pending_approval and the account owner approves by replying APPROVE. Set false ONLY when the human has explicitly waived approval.
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it creates a draft, nothing sends, approvalRequired parks for human approval, audience gating logic, and that drafting is free. No hidden side effects 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient paragraph with no wasted words. It front-loads the critical action and provides essential details in a logical order. Every sentence contributes meaning.

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?

Given no output schema, the description does not need to explain return values. It covers input parameters comprehensively and organizes them logically. It could mention that the campaign ID is returned, but the description is already very complete for agent decision-making.

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. The description adds significant value by explaining the overall logic (audience, content options, approval) and constraints like 'never both' for template vs inline content, going beyond individual parameter descriptions.

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 it creates a campaign DRAFT and explicitly distinguishes from send_campaign. It specifies the verb 'Create', the resource 'campaign', and the state 'DRAFT'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool (to create a draft), contrasts with send_campaign, explains audience selection via segmentId/topicId, content options (templateId vs inline), and the approvalRequired flag with default behavior.

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/ATOM00blue/drin-mcp'

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