Skip to main content
Glama

Nevent MCP

by io.github.nevent-dev

nevent_create_campaign

Create a new campaign draft (email, SMS, WhatsApp, push, or multi-channel). PREREQUISITES: call nevent_list_segments to get the target segment_id, and nevent_list_templates to get the template_id. The campaign is always created in DRAFT status — no messages are sent. After creation, call nevent_schedule_campaign to schedule delivery. For EMAIL_ONLY (and email multi-channel): email_subject is required. For SMS_ONLY/WHATSAPP_ONLY/PUSH_ONLY and multi-channel involving those: message is required. Optional fields: from_name, preview_text, template_id, segment_ids, utm_source/medium/campaign/content/term/custom_params, reply_to (email address for reply routing — useful when replies should go to a different mailbox than the From address). Always confirm the segment audience count with the user before scheduling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCampaign name (required, max 255 characters)
channelYesDelivery channel (nev-api CommunicationChannel enum). Use EMAIL_ONLY, SMS_ONLY, WHATSAPP_ONLY, PUSH_ONLY for single-channel; EMAIL_AND_SMS, EMAIL_AND_WHATSAPP, PUSH_AND_SMS, PUSH_AND_WHATSAPP, SMS_AND_WHATSAPP for multi-channel; ALL_CHANNELS or OMNICHANNEL for broad delivery. Legacy values EMAIL/SMS/WHATSAPP are accepted but deprecated.
messageNoMessage text body (required when channel=SMS or WHATSAPP)
reply_toNoReply-To email address (optional). Recipients' replies go to this address instead of the From address. Must be a valid email, max 254 chars. Only meaningful for email-bearing channels.
utm_termNoUTM term parameter — paid search keyword. Max 100 chars.
from_nameNoSender display name (optional, defaults to tenant sender name)
email_bodyNoHTML body content of the email (optional, can be set later)
utm_mediumNoUTM medium parameter (e.g. "email", "sms"). Max 100 chars. Auto-detected from channel if omitted.
utm_sourceNoUTM source parameter (e.g. "nevent", "newsletter"). Max 100 chars.
segment_idsNoArray of segment IDs to target (optional, can be set later)
template_idNoTemplate ID to pre-populate campaign content (optional)
utm_contentNoUTM content parameter — differentiates links/variants. Max 100 chars.
preview_textNoInbox preview text (optional, shown in email client summaries)
utm_campaignNoUTM campaign parameter (e.g. "summer-sale-2026"). Max 100 chars. Defaults to slugified campaign name.
email_subjectNoEmail subject line (required when channel=EMAIL, max 998 chars per RFC 5322)
utm_custom_paramsNoCustom tracking parameters as key-value pairs appended to tracked links (optional).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

It clearly discloses a key behavioral trait: 'The campaign is always created in DRAFT status — no messages are sent.' This goes beyond the readOnlyHint/destructiveHint annotations and directly addresses the main risk of a campaign-creation tool. It also adds a useful safety instruction to confirm the segment audience count before scheduling.

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 well organized: overview, prerequisites, status, next step, required fields, optional fields, and safety guardrail. It is dense and front-loaded, though the optional-field list partly repeats schema information and adds to the overall length. For a 16-parameter tool this is acceptable.

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?

Combined with the input schema's full property coverage, the description covers the core purpose, draft semantics, channel-specific requirements, and the follow-up scheduling step. It does not mention the return value, and it does not explicitly address required fields for ALL_CHANNELS/OMNICHANNEL, but the schema enum and the deprecation notes cover much of that context.

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%, so the baseline is 3. The description adds channel-conditional required-field guidance and explains when reply_to is useful, but it also introduces inconsistencies: it says 'segment_id' while the schema property is segment_ids, treats optional template_id/segment_ids as prerequisites, omits email_body from the optional-field list, and its message-required rule for PUSH/multi-channel is not reflected in the schema's property 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 opens with a specific verb and object — 'Create a new campaign draft' — and enumerates the supported channel types. It clearly distinguishes itself from sibling tools by emphasizing that the result is only a DRAFT and that no messages are sent, which separates it from nevent_schedule_campaign.

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

Usage Guidelines4/5

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

The description provides an explicit workflow: fetch segment and template IDs first, create the draft, then call nevent_schedule_campaign, and confirm audience count before scheduling. However, it frames segment_ids and template_id as prerequisites even though the schema marks them optional, which slightly overstates when this tool must be used.

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

All Nevent MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Most domain groups are distinct, but the campaign reporting cluster has three tools returning overlapping engagement metrics (get_campaign, get_campaign_metrics, campaign_report), and paid_ads_status vs paid_ads_health have fuzzy boundaries. The detailed descriptions mitigate but do not eliminate the risk of an agent calling the wrong tool.

Naming Consistency3/5

All names use the nevent_ prefix and snake_case, and most CRUD operations follow verb_noun. However, several tools reverse the order or drop the verb entirely (segment_preview, segment_execute, campaign_report, paid_ads_status, analytics_query), making the convention mixed but still readable.

Tool Count1/5

With 59 tools, this is far above the 25+ 'too many' threshold and falls into the 50+ extreme range. The broad domain coverage explains some of the size, but for an agent the set is likely to be overwhelming and harder to navigate than a more focused server.

Completeness3/5

The core marketing workflow (segments, templates, campaign creation, quote, schedule, metrics) is covered, but there is no way to update, cancel, or delete a campaign, and templates and segments lack delete operations. These are notable lifecycle gaps that agents will hit when users want to change or clean up resources.

Resources