Skip to main content
Glama
Ringer

warp-mcp

by Ringer

Create 10DLC campaign

msg_create_campaign

Register a new 10DLC campaign under your brand for A2P messaging. Submit sample messages, consent flow, and opt-in rules for carrier review and approval.

Instructions

Register a new 10DLC campaign under one of your brands. This is STEP 2 of the 10DLC flow: msg_create_brand → create campaign → msg_assign_numbers. Check msg_get_use_case_requirements for the chosen use case first (sample counts, opt-in rules). Carrier review can take days; monitor with msg_get_mno_status. Registration incurs recurring TCR fees. Errors: INVALID_PAYLOAD/TNIQ_VALIDATION (400), TNIQ_ERROR (502).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sample1NoSample message 1 (representative outbound text)
sample2NoSample message 2
sample3NoSample message 3
sample4NoSample message 4
sample5NoSample message 5
usecaseNoCampaign use case code, e.g. MARKETING, 2FA, CUSTOMER_CARE (see msg_list_use_cases; check msg_get_use_case_requirements first)
brand_idNoParent brand ID (messaging-backend UUID from msg_list_brands). Required when creating a campaign.
age_gatedNoTrue if content is age-gated (alcohol, gambling, etc.)
descriptionNoWhat this campaign sends and to whom (reviewed by carriers)
number_poolNoTrue if the campaign uses 50+ sending numbers (number pooling)
auto_renewalNoAuto-renew the campaign at TCR each billing cycle
help_messageNoReply sent when a subscriber texts a help keyword
message_flowNoHow subscribers opt in to receive messages (consent flow description; heavily weighted in carrier review)
reference_idNoYour own free-form reference ID for this campaign
sub_usecasesNoSub-use-case codes for MIXED/LOW_VOLUME campaigns
embedded_linkNoTrue if messages may contain URLs/links
help_keywordsNoComma-separated help keywords, e.g. "HELP,INFO"
optin_messageNoConfirmation message sent after a subscriber opts in
direct_lendingNoTrue if content relates to direct lending or loan arrangements
embedded_phoneNoTrue if messages may contain phone numbers
optin_keywordsNoComma-separated opt-in keywords, e.g. "START,SUBSCRIBE"
optout_messageNoConfirmation message sent after a subscriber opts out
optout_keywordsNoComma-separated opt-out keywords, e.g. "STOP,UNSUBSCRIBE"
subscriber_helpNoTrue if subscribers can request help via keyword (HELP handling)
subscriber_optinNoTrue if subscribers can opt in via keyword
subscriber_optoutNoTrue if subscribers can opt out via keyword (STOP handling)
terms_and_conditionsNoAffirm the campaign complies with carrier terms and conditions
Behavior4/5

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

Adds important behavioral context beyond annotations: carrier review can take days, incurs recurring TCR fees, and lists specific error codes (400, 502). No contradiction with annotations (readOnlyHint, destructiveHint all false).

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?

Four sentences, each with distinct value: main purpose, flow position, prerequisites, and behavioral notes. No wasted words, proceeds from high-level to specifics.

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 the tool's complexity (27 parameters, no output schema, multi-step flow), the description covers purpose, prerequisites, post-actions, and errors. Missing explicit note about what the response returns (e.g., campaign ID), but well-rounded otherwise.

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 description coverage is 100% with detailed descriptions for each of the 27 parameters. The tool description adds minimal new parameter information; it mentions sample counts and opt-in rules which are already covered by schema parameters. Baseline 3 is appropriate.

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?

Clearly states 'Register a new 10DLC campaign under one of your brands', identifies the resource and action. Explicitly positions it as STEP 2 in a three-step flow (msg_create_brand → create campaign → msg_assign_numbers), distinguishing it from sibling tools.

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?

Provides sequential context (step 2 of the 10DLC flow) and directs to check use case requirements and monitor carrier review. Implicitly tells when to use (after brand creation, before number assignment) though lacks explicit 'when not to use' or alternative scenarios.

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/Ringer/warp-mcp'

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